CVE-2026-82067

HIGHPre-NVD 8.18.1—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.1EG
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.1Exploit: None knownExposed: 0

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

Improper handling of case sensitivity in the configuration validation component of MongoDB Server may cause the authorization subsystem to remain in a default disabled state during server startup. An unauthenticated user with network access to a deployment where this condition occurs can perform arbitrary administrative operations, resulting in full impact of data confidentiality, integrity, and availability.

CVSS v3
8.1
EG Score
8.1(high)
EG Risk
37(Track)
EG Risk 37/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
Severity81% × 45%
Exploitation0% × 40%
Automatability0% × 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.
generic

Loading...

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

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

Frequently asked(5)

What is CVE-2026-82067?
CVE-2026-82067 is a high vulnerability published on September 8, 2026. Improper handling of case sensitivity in the configuration validation component of MongoDB Server may cause the authorization subsystem to remain in a default disabled state during server startup. An unauthenticated user with network access to a deployment where this condition occurs can perform…
When was CVE-2026-82067 disclosed?
CVE-2026-82067 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-82067 actively exploited?
CVE-2026-82067 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 79.2% of all scored CVEs.
What is the CVSS score of CVE-2026-82067?
CVE-2026-82067 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-82067?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-82067, 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-82067

Explore →

Is Your Infrastructure Affected by CVE-2026-82067?

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

Start Free Scan →Browse All CVEs