CVE-2026-94393

MEDIUMPre-NVD 6.46.4—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 72% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 4 sources updated this week
6.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.4Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

When a user creates or edits a report inside an event, MISP can identify an existing report using its UUID without properly checking whether that report actually belongs to the same event.

As a result, a user who has editing rights on one event could potentially move a report from another event into their own event, as long as they know or can guess the report’s UUID. Once moved, they could view and change information that they were not originally allowed to access.

The vulnerability requires the attacker to have editor access to at least one event and to know or discover a valid report UUID.

The main impact is that private event reports could be exposed or modified across event boundaries, bypassing MISP’s normal access restrictions.

Version affected: <2.5.47

CVSS v3
6.4
EG Score
6.4(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity64% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
28%
KEV
Not listed

Published

September 21, 2026

Last Modified

September 21, 2026

Advisory Details (1)

Auto-updated Sep 21, 2026
Patch available. Sources: github_commit.
github_commit Patch Available

commit 43665b9bb (MISP/MISP)

Patch available: MISP/MISP v2.5.47 (contains commit 43665b9bb)

https://github.com/MISP/MISP/commit/43665b9bb

Vendor Advisories for CVE-2026-94393(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 16× in last 7d / 16× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-25 09:20 UTCEG score recompute
  2. 2026-09-25 09:20 UTCGHSA enrichment
  3. 2026-09-24 14:04 UTCEPSS rescore
  4. 2026-09-24 11:06 UTCEG score recompute
  5. 2026-09-24 11:06 UTCGHSA enrichment
  6. 2026-09-23 17:54 UTCEPSS rescore
  7. 2026-09-23 12:53 UTCEG score recompute
  8. 2026-09-23 12:53 UTCGHSA enrichment
  9. 2026-09-22 16:01 UTCEPSS rescore
  10. 2026-09-22 14:39 UTCGHSA enrichment
  11. 2026-09-21 16:24 UTCEG score recompute
  12. 2026-09-21 16:24 UTCGHSA enrichment
  13. 2026-09-21 15:30 UTCEG score recompute
  14. 2026-09-21 14:21 UTCEG score recompute
  15. 2026-09-21 13:20 UTCEG score recompute
  16. 2026-09-21 13:20 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-94393?
CVE-2026-94393 is a medium vulnerability published on September 21, 2026. When a user creates or edits a report inside an event, MISP can identify an existing report using its UUID without properly checking whether that report actually belongs to the same event. As a result, a user who has editing rights on one event could potentially move a report from another event…
When was CVE-2026-94393 disclosed?
CVE-2026-94393 was first published in the National Vulnerability Database on September 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-94393 actively exploited?
CVE-2026-94393 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 71.7% of all scored CVEs.
What is the CVSS score of CVE-2026-94393?
CVE-2026-94393 has a CVSS v3 base score of 6.4 (NVD).
How do I remediate CVE-2026-94393?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-94393, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-94393

Explore →

Is Your Infrastructure Affected by CVE-2026-94393?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs