CVE-2026-82076

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreHIGH confidence

Score 6.5 from GitHub Security Advisory (severity: HIGH) published 2026-09-08. a secondary CVSS source baseline 6.5; sources differ by 0.0.

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

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

An integer overflow in the query planning component of MongoDB Server can allow an authenticated user with ordinary database-level read/write privileges to bypass an internal resource limit. Submitting a specially crafted query causes the server to consume memory without bound during query planning, and the resulting exhaustion terminates the server process. This may result in a denial of service affecting all databases served by the affected node.

CVSS v3
6.5
EG Score
6.5(high)
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
Severity65% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
22%
KEV
Not listed

Published

September 8, 2026

Last Modified

September 14, 2026

Advisory Details (1)

Auto-updated Sep 8, 2026
No patch confirmed yet.
generic

Loading...

https://jira.mongodb.org/browse/SERVER-128253

Vendor Advisories for CVE-2026-82076(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 19× in last 7d / 35× 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-21 05:15 UTCEG score recompute
  2. 2026-09-21 05:15 UTCGHSA enrichment
  3. 2026-09-20 20:16 UTCEPSS rescore
  4. 2026-09-20 03:28 UTCEG score recompute
  5. 2026-09-20 03:28 UTCGHSA enrichment
  6. 2026-09-19 01:42 UTCEG score recompute
  7. 2026-09-19 01:42 UTCGHSA enrichment
  8. 2026-09-18 19:28 UTCEPSS rescore
  9. 2026-09-17 23:55 UTCEG score recompute
  10. 2026-09-17 23:55 UTCGHSA enrichment
  11. 2026-09-16 21:28 UTCEG score recompute
  12. 2026-09-16 21:28 UTCGHSA enrichment
  13. 2026-09-16 14:08 UTCEPSS rescore
  14. 2026-09-16 05:15 UTCEPSS rescore
  15. 2026-09-15 19:42 UTCEG score recompute
  16. 2026-09-15 19:42 UTCGHSA enrichment
  17. 2026-09-15 03:12 UTCEPSS rescore
  18. 2026-09-15 03:12 UTCEPSS rescore
  19. 2026-09-14 17:54 UTCGHSA enrichment
  20. 2026-09-14 06:12 UTCEG score recompute
  21. 2026-09-14 06:12 UTCGHSA enrichment
  22. 2026-09-13 04:26 UTCEG score recompute
  23. 2026-09-13 04:26 UTCGHSA enrichment
  24. 2026-09-12 02:39 UTCEG score recompute
  25. 2026-09-12 02:39 UTCGHSA enrichment
Show 10 more
  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-11 14:53 UTCEPSS rescore
  3. 2026-09-11 00:52 UTCEG score recompute
  4. 2026-09-11 00:52 UTCGHSA enrichment
  5. 2026-09-09 23:06 UTCGHSA enrichment
  6. 2026-09-08 19:48 UTCEG score recompute
  7. 2026-09-08 19:48 UTCGHSA enrichment
  8. 2026-09-08 18:13 UTCEG score recompute
  9. 2026-09-08 16:28 UTCEG score recompute
  10. 2026-09-08 16:25 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-82076?
CVE-2026-82076 is a medium vulnerability published on September 8, 2026. An integer overflow in the query planning component of MongoDB Server can allow an authenticated user with ordinary database-level read/write privileges to bypass an internal resource limit. Submitting a specially crafted query causes the server to consume memory without bound during query…
When was CVE-2026-82076 disclosed?
CVE-2026-82076 was first published in the National Vulnerability Database on September 8, 2026, with the most recent update on September 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-82076 actively exploited?
CVE-2026-82076 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 78.2% of all scored CVEs.
What is the CVSS score of CVE-2026-82076?
CVE-2026-82076 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-82076?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-82076, 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-82076

Explore →

Is Your Infrastructure Affected by CVE-2026-82076?

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

Start Free Scan →Browse All CVEs