CVE-2026-112178

waiting for further signalsZero needs more public information before it can validate it.

GHSA-9h3q-39v8-fmg5 ↗EUVD-2026-104127 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
MISP < 2.5.48
fixed in 2.5.48
CWE-862 Missing Authorization
ETK-2026-2152Zero's internal tracking ID, independent of the CVE number., permanent identifier
20h 15msince last run
1h 01mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+25h39m
0
+2h
+4h
+6h
+8h
+10h

description

MISP versions before 2.5.48 incorrectly evaluate access to proposed attribute and object changes. A user in a relevant sharing group may view proposals that their distribution settings should withhold from them.

mitigation

Upgrade MISP to version 2.5.48. Until upgrade is complete, review and limit membership in sharing groups that can expose restricted proposals.

fixed in 2.5.48

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.23%12th percentile
agent run time
1h 01m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-19 08:50Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-19 08:50Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-112178

{
  "etk_id": "ETK-2026-2152",
  "cve_id": "CVE-2026-112178",
  "display_id": "CVE-2026-112178",
  "ghsa_id": "GHSA-9h3q-39v8-fmg5",
  "euvd_id": "EUVD-2026-104127",
  "status": "published",
  "anchor_state": "anchored",
  "title": "MISP proposal visibility authorization bypass",
  "summary": "MISP versions before 2.5.48 incorrectly evaluate access to proposed attribute and object changes. A user in a relevant sharing group may view proposals that their distribution settings should withhold from them.",
  "mitigation": "Upgrade MISP to version 2.5.48. Until upgrade is complete, review and limit membership in sharing groups that can expose restricted proposals.",
  "vendor": "MISP",
  "product": "MISP",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 2.5.48"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "2.5.48"
      ],
      "package_name": "MISP",
      "purl": null
    }
  ],
  "cwes": [
    862
  ],
  "cvss_score": 7.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N",
  "epss_score": 0.0023,
  "epss_percentile": 0.1295,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 61.278362466666664,
  "t0_at": "2026-10-19T08:50:52.402000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-19T08:50:52.402000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-19T08:50:52.402000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-112178"
    }
  }
}

published 2026-10-20 09:28Z
last change 2026-10-21 05:31Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.