CVE-2026-88036

HIGHPre-NVD 8.38.3
EchelonGraph scoreHIGH confidence

Score 8.3 from GitHub Security Advisory published 2026-09-10. a secondary CVSS source baseline 8.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.3Exploit: None knownExposed: 0

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

Improper neutralization of special elements in data query logic in the GridFS component of the MongoDB C Driver can cause a caller-supplied structured file identifier to be interpreted as a query condition rather than as a literal identifier. An authenticated user who can influence the identifier passed by an affected application may obtain stored file content beyond the intended target or cause all GridFS file chunks in the affected bucket to be removed, rendering stored file content unreadable.

CVSS v3
8.3
EG Score
8.3(high)
EG Risk
42(Track)
EG Risk 42/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
Severity83% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
19%
KEV
Not listed

Published

September 10, 2026

Last Modified

September 16, 2026

Advisory Details (1)

Auto-updated Sep 10, 2026
No patch confirmed yet.

Vendor Advisories for CVE-2026-88036(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 30× in last 7d / 40× 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-19 00:49 UTCEG score recompute
  2. 2026-09-19 00:49 UTCGHSA enrichment
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-18 13:57 UTCGHSA enrichment
  5. 2026-09-18 03:04 UTCEG score recompute
  6. 2026-09-18 03:04 UTCGHSA enrichment
  7. 2026-09-17 19:32 UTCEPSS rescore
  8. 2026-09-17 16:12 UTCGHSA enrichment
  9. 2026-09-17 05:19 UTCGHSA enrichment
  10. 2026-09-16 18:27 UTCGHSA enrichment
  11. 2026-09-16 18:09 UTCEG score recompute
  12. 2026-09-16 18:08 UTCGHSA enrichment
  13. 2026-09-16 14:09 UTCEPSS rescore
  14. 2026-09-16 06:34 UTCEG score recompute
  15. 2026-09-16 06:34 UTCGHSA enrichment
  16. 2026-09-16 05:15 UTCEPSS rescore
  17. 2026-09-15 19:42 UTCGHSA enrichment
  18. 2026-09-15 08:41 UTCEG score recompute
  19. 2026-09-15 08:41 UTCGHSA enrichment
  20. 2026-09-15 03:12 UTCEPSS rescore
  21. 2026-09-14 21:48 UTCGHSA enrichment
  22. 2026-09-14 10:56 UTCGHSA enrichment
  23. 2026-09-14 00:04 UTCEG score recompute
  24. 2026-09-14 00:04 UTCGHSA enrichment
  25. 2026-09-13 16:48 UTCEPSS rescore
Show 15 more
  1. 2026-09-13 13:12 UTCGHSA enrichment
  2. 2026-09-13 02:20 UTCGHSA enrichment
  3. 2026-09-12 15:27 UTCEG score recompute
  4. 2026-09-12 15:27 UTCGHSA enrichment
  5. 2026-09-12 15:02 UTCEPSS rescore
  6. 2026-09-12 04:35 UTCGHSA enrichment
  7. 2026-09-11 17:42 UTCEG score recompute
  8. 2026-09-11 17:42 UTCGHSA enrichment
  9. 2026-09-11 14:53 UTCEPSS rescore
  10. 2026-09-11 14:53 UTCEPSS rescore
  11. 2026-09-11 06:50 UTCEG score recompute
  12. 2026-09-11 06:50 UTCGHSA enrichment
  13. 2026-09-10 19:18 UTCEG score recompute
  14. 2026-09-10 18:25 UTCEG score recompute
  15. 2026-09-10 18:24 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-88036?
CVE-2026-88036 is a high vulnerability published on September 10, 2026. Improper neutralization of special elements in data query logic in the GridFS component of the MongoDB C Driver can cause a caller-supplied structured file identifier to be interpreted as a query condition rather than as a literal identifier. An authenticated user who can influence the identifier…
When was CVE-2026-88036 disclosed?
CVE-2026-88036 was first published in the National Vulnerability Database on September 10, 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-88036 actively exploited?
CVE-2026-88036 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 81.3% of all scored CVEs.
What is the CVSS score of CVE-2026-88036?
CVE-2026-88036 has a CVSS v3 base score of 8.3 (NVD).
How do I remediate CVE-2026-88036?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-88036, 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-88036

Explore →

Is Your Infrastructure Affected by CVE-2026-88036?

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