A missing input-validation issue in MongoDB libmongocrypt's automatic-encryption context setup allows a caller-supplied database identifier to be accepted without sanitization. The resulting impact is limited to incorrect schema selection, which may lead to limited disclosure or modification of information handled by the application.
CVE-2026-81523
This medium-severity CVE scores 4.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 100% 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).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.4
- EG Score
- 4.4(medium)
- EG Risk
- 20(Track)EG Risk 20/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 computedSeverity44% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 0%
- KEV
- Not listed
Published
August 27, 2026
Last Modified
August 28, 2026
Advisory Details (1)
Auto-updated Aug 27, 20261.20.3 release
Patch available: mongodb/libmongocrypt 1.20.3
https://github.com/mongodb/libmongocrypt/releases/tag/1.20.3Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 10× 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.
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 20:54 UTCEG score recompute
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-28 20:42 UTCEG score recompute
- 2026-08-28 19:47 UTCEG score recompute
- 2026-08-28 00:32 UTCEG score recompute
- 2026-08-27 23:24 UTCEG score recompute
- 2026-08-27 20:26 UTCEG score recompute
- 2026-08-27 20:15 UTCEG score recompute
- 2026-08-27 20:13 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-74
- CVE-2014-8423EG 10.0EPSS p99HIGH
- CVE-2015-10062NVD 5.5EG 9.8CRITICAL
- CVE-2015-10027NVD 5.5EG 9.8CRITICAL
- CVE-2016-15007NVD 5.5EG 9.8CRITICAL
- CVE-2016-15004NVD 7.3EG 9.8CRITICAL
- CVE-2013-4144EG 9.8CRITICAL
- CVE-2013-7487EG 9.8CRITICAL
- CVE-2014-4678EG 9.8EPSS p92CRITICAL
- CVE-2014-4967EG 9.8CRITICAL
- CVE-2014-4966EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-81523?
When was CVE-2026-81523 disclosed?
Is CVE-2026-81523 actively exploited?
What is the CVSS score of CVE-2026-81523?
How do I remediate CVE-2026-81523?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-81523
Is Your Infrastructure Affected by CVE-2026-81523?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.