CVE-2026-82075

HIGHPre-NVD 7.57.5
EchelonGraph scoreHIGH confidence

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

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

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

An uncontrolled resource consumption weakness exists in the request-handling path of the MongoDB sharded-cluster router process. A client that has network access to a router port and has not authenticated can supply connection-monitoring parameters that cause the server to expend CPU resources without any rate limiting, degrading or denying service to legitimate clients. No authentication, elevated privileges, or user interaction is required. Only availability is affected; data confidentiality and integrity are not impacted.

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

Published

September 8, 2026

Last Modified

September 16, 2026

Advisory Details (1)

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

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

Frequently asked(5)

What is CVE-2026-82075?
CVE-2026-82075 is a high vulnerability published on September 8, 2026. An uncontrolled resource consumption weakness exists in the request-handling path of the MongoDB sharded-cluster router process. A client that has network access to a router port and has not authenticated can supply connection-monitoring parameters that cause the server to expend CPU resources…
When was CVE-2026-82075 disclosed?
CVE-2026-82075 was first published in the National Vulnerability Database on September 8, 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-82075 actively exploited?
CVE-2026-82075 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.5% of all scored CVEs.
What is the CVSS score of CVE-2026-82075?
CVE-2026-82075 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-82075?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-82075, 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-82075

Explore →

Is Your Infrastructure Affected by CVE-2026-82075?

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