CVE-2026-91859

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreMEDIUM confidence

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

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

Affected versions of MISP can record incorrect access-log data for requests that terminate in an exception.

Because CakeErrorController extends AppController, exception rendering runs the application startup path a second time. As a result, __accessMonitor() calls AccessLog::logRequest() twice for one HTTP request. The second deferred writer measures the error-controller execution instead of the original request and can overwrite the row created by the first pass. The corrupted fields include request duration, SQL query count, memory usage, and potentially the recorded query log.

The bug was masked because the same model instance retained the ID of the first saved row, causing the later save to issue an UPDATE rather than insert an obvious duplicate row.

Version affected: ≤2.5.45

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
24(Track)
EG Risk 24/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
Severity53% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
23%
KEV
Not listed

Published

September 15, 2026

Last Modified

September 16, 2026

Advisory Details (1)

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

commit 0dae5c072 (MISP/MISP)

Patch available: MISP/MISP v2.5.46 (contains commit 0dae5c072)

https://github.com/MISP/MISP/commit/0dae5c072

Vendor Advisories for CVE-2026-91859(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 15× in last 7d / 15× 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-18 19:28 UTCEPSS rescore
  2. 2026-09-18 17:34 UTCEG score recompute
  3. 2026-09-18 17:34 UTCGHSA enrichment
  4. 2026-09-17 19:32 UTCEPSS rescore
  5. 2026-09-17 15:39 UTCEG score recompute
  6. 2026-09-17 15:39 UTCGHSA enrichment
  7. 2026-09-16 14:09 UTCEPSS rescore
  8. 2026-09-16 13:44 UTCEG score recompute
  9. 2026-09-16 13:44 UTCGHSA enrichment
  10. 2026-09-16 05:15 UTCEPSS rescore
  11. 2026-09-15 13:18 UTCEG score recompute
  12. 2026-09-15 13:18 UTCGHSA enrichment
  13. 2026-09-15 10:28 UTCEG score recompute
  14. 2026-09-15 09:43 UTCEG score recompute
  15. 2026-09-15 09:42 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-91859?
CVE-2026-91859 is a medium vulnerability published on September 15, 2026. Affected versions of MISP can record incorrect access-log data for requests that terminate in an exception. Because CakeErrorController extends AppController, exception rendering runs the application startup path a second time. As a result, accessMonitor() calls AccessLog::logRequest() twice for…
When was CVE-2026-91859 disclosed?
CVE-2026-91859 was first published in the National Vulnerability Database on September 15, 2026, with the most recent update on September 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-91859 actively exploited?
CVE-2026-91859 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 77.5% of all scored CVEs.
What is the CVSS score of CVE-2026-91859?
CVE-2026-91859 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-91859?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-91859, 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-91859

Explore →

Is Your Infrastructure Affected by CVE-2026-91859?

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