CVE-2026-81522

HIGHPre-NVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 82% 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 — 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.

A weakness in the MongoDB C++ Driver's handling of caller-supplied namespace identifiers allows special characters embedded in those identifiers. An application that builds a namespace identifier from untrusted input without validating it may therefore have its operation directed at a different target than intended. This can result in limited unauthorized read and write access to data belonging to another logical tenant of the affected application.

CVSS v3
8.1
EG Score
8.1(medium)
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
18%
KEV
Not listed

Published

August 27, 2026

Last Modified

August 29, 2026

Advisory Details (1)

Auto-updated Aug 27, 2026
Patch available. Sources: github_release.
github_release Patch Available

MongoDB C++11 Driver r4.5.1

Patch available: mongodb/mongo-cxx-driver r4.5.1

https://github.com/mongodb/mongo-cxx-driver/releases/tag/r4.5.1

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 11× 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-08-30 01:22 UTCEPSS rescore
  2. 2026-08-29 04:28 UTCEG score recompute
  3. 2026-08-29 04:06 UTCEG score recompute
  4. 2026-08-28 21:42 UTCEPSS rescore
  5. 2026-08-28 20:42 UTCEG score recompute
  6. 2026-08-28 19:47 UTCEG score recompute
  7. 2026-08-28 00:32 UTCEG score recompute
  8. 2026-08-27 23:25 UTCEG score recompute
  9. 2026-08-27 20:26 UTCEG score recompute
  10. 2026-08-27 20:15 UTCEG score recompute
  11. 2026-08-27 20:13 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-81522?
CVE-2026-81522 is a high vulnerability published on August 27, 2026. A weakness in the MongoDB C++ Driver's handling of caller-supplied namespace identifiers allows special characters embedded in those identifiers. An application that builds a namespace identifier from untrusted input without validating it may therefore have its operation directed at a different…
When was CVE-2026-81522 disclosed?
CVE-2026-81522 was first published in the National Vulnerability Database on August 27, 2026, with the most recent update on August 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-81522 actively exploited?
CVE-2026-81522 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.9% of all scored CVEs.
What is the CVSS score of CVE-2026-81522?
CVE-2026-81522 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-81522?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-81522, 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-81522

Explore →

Is Your Infrastructure Affected by CVE-2026-81522?

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

Start Free Scan →Browse All CVEs