CVE-2026-95679

MEDIUMPre-NVD 6.96.9—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6%, top 53% 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.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 6.9Exploit: None knownExposed: 0

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

MISP's RequestHandlerComponent automatically decodes XML request bodies on all write requests. The underlying Xml::build() library contains a logic error in its readFile guard condition (readFile && http || https), where PHP operator precedence causes the https branch to bypass the readFile check entirely. As a result, a request body containing a bare HTTPS URL is treated as a locator and fetched by the server. Because the cspReport endpoint accepts XML content type and is unauthenticated by design, an unauthenticated remote attacker can send a POST request with a crafted XML body to cause the MISP server to issue an outbound HTTPS request to an arbitrary target reachable from the server.

The attacker does not receive the response body, but can use the vulnerability to probe internal services, trigger actions on internal HTTPS endpoints, or perform timing-based reconnaissance of the server's network environment. 

The vulnerability affects any MISP deployment where the cspReport endpoint is reachable and the server has network access to internal or external HTTPS services.

CVSS v3
6.9
EG Score
6.9(medium)
EG Risk
46(Track)
EG Risk 46/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
Severity69% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
46%
KEV
Not listed

Published

September 22, 2026

Last Modified

September 22, 2026

Advisory Details (1)

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

commit 716fc49d3 (MISP/MISP)

Patch available: MISP/MISP v2.5.47 (contains commit 716fc49d3)

https://github.com/MISP/MISP/commit/716fc49d3

Vendor Advisories for CVE-2026-95679(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 12× in last 7d / 12× 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-24 14:04 UTCEPSS rescore
  2. 2026-09-24 13:16 UTCEG score recompute
  3. 2026-09-24 13:16 UTCGHSA enrichment
  4. 2026-09-23 17:54 UTCEPSS rescore
  5. 2026-09-23 14:48 UTCGHSA enrichment
  6. 2026-09-22 16:21 UTCEG score recompute
  7. 2026-09-22 16:21 UTCGHSA enrichment
  8. 2026-09-22 15:45 UTCEG score recompute
  9. 2026-09-22 15:45 UTCGHSA enrichment
  10. 2026-09-22 14:19 UTCEG score recompute
  11. 2026-09-22 13:56 UTCEG score recompute
  12. 2026-09-22 13:55 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-95679?
CVE-2026-95679 is a medium vulnerability published on September 22, 2026. MISP's RequestHandlerComponent automatically decodes XML request bodies on all write requests. The underlying Xml::build() library contains a logic error in its readFile guard condition (readFile && http || https), where PHP operator precedence causes the https branch to bypass the readFile check…
When was CVE-2026-95679 disclosed?
CVE-2026-95679 was first published in the National Vulnerability Database on September 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-95679 actively exploited?
CVE-2026-95679 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 53.6% of all scored CVEs.
What is the CVSS score of CVE-2026-95679?
CVE-2026-95679 has a CVSS v3 base score of 6.9 (NVD).
How do I remediate CVE-2026-95679?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-95679, 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-95679

Explore →

Is Your Infrastructure Affected by CVE-2026-95679?

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