CVE-2026-81523

MEDIUMPre-NVD 4.44.4
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 4.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: <0.1% (below the 1st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-67207 (ENISA EUVD)Source: ENISA EUVD

4.4EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: <0.1%CVSS: 4.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
4.4
EG Score
4.4MEDIUMmedium confidence
EG Risk
20
EG Risk 20/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity44% × 45%
Impact severity (EG Severity): CVSS 4.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
<0.1%
EPSS %ILE
below the 1st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (4.4): severity, escalated by confirmed exploitation. This CVE's 4.4 is its impact severity (EG Severity), not escalated.

EG Severity
4.4 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
<0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 27, 2026

Last Modified

September 17, 2026

Advisory Details (1)

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

1.20.3 release

Patch available: mongodb/libmongocrypt 1.20.3

https://github.com/mongodb/libmongocrypt/releases/tag/1.20.3

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
libmongocrypt1.10.0-1 ... 1.9.1-1 (23 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
libmongocrypt1.13.2-1
  • every version up to 1.13.2-1+deb13u1: fixed in 1.13.2-1+deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
libmongocrypt1.13.2-1 ... 1.20.2-1 (11 versions)
  • every version up to 1.20.3-1: fixed in 1.20.3-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 23× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 81 is merged into the row it repeats.

  1. 2026-11-13 16:57 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  2. 2026-11-12 16:34 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  3. 2026-11-11 16:40 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  4. 2026-11-10 16:45 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  5. 2026-11-08 16:41 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  6. 2026-11-07 16:40 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  7. 2026-11-06 16:39 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  8. 2026-11-05 16:38 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  9. 2026-11-04 16:37 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  10. 2026-11-03 16:49 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  11. 2026-11-02 16:46 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  12. 2026-11-01 16:35 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  13. 2026-10-31 16:33 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  14. 2026-10-30 16:35 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  15. 2026-10-30 01:55 UTCOSV refresh
  16. 2026-10-28 16:33 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  17. 2026-10-26 16:32 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  18. 2026-10-25 16:34 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  19. 2026-10-25 13:58 UTCEchelonGraph re-scored
  20. 2026-10-24 16:33 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  21. 2026-10-22 13:49 UTCEchelonGraph re-scored
  22. 2026-10-20 16:33 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  23. 2026-10-19 16:33 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  24. 2026-10-18 03:09 UTCEchelonGraph re-scored
  25. 2026-10-16 16:44 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
Show 55 more
  1. 2026-10-15 16:33 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  2. 2026-10-14 16:33 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  3. 2026-10-13 16:35 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  4. 2026-10-12 16:35 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  5. 2026-10-12 14:56 UTCEchelonGraph re-scored
  6. 2026-10-11 19:20 UTCEchelonGraph re-scored
  7. 2026-10-11 16:37 UTCEchelonGraph re-scored
  8. 2026-10-11 13:55 UTCEchelonGraph re-scored
  9. 2026-10-11 13:49 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  10. 2026-10-10 20:00 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  11. 2026-10-09 06:10 UTCEchelonGraph re-scored
  12. 2026-10-08 17:13 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  13. 2026-10-08 06:38 UTCEchelonGraph re-scored
  14. 2026-10-07 23:48 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  15. 2026-10-07 07:06 UTCEchelonGraph re-scored
  16. 2026-10-06 15:18 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  17. 2026-10-05 05:06 UTCEchelonGraph re-scored
  18. 2026-10-04 23:22 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  19. 2026-10-02 06:18 UTCEchelonGraph re-scored
  20. 2026-10-01 19:50 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  21. 2026-10-01 04:26 UTCEchelonGraph re-scored
  22. 2026-09-30 15:04 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  23. 2026-09-30 04:54 UTCEchelonGraph re-scored
  24. 2026-09-27 17:58 UTCEchelonGraph re-scored
  25. 2026-09-27 13:48 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  26. 2026-09-26 18:24 UTCEchelonGraph re-scored
  27. 2026-09-26 15:59 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  28. 2026-09-25 10:13 UTCEchelonGraph re-scored
  29. 2026-09-24 14:04 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  30. 2026-09-24 10:41 UTCEchelonGraph re-scored
  31. 2026-09-23 17:54 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  32. 2026-09-20 12:36 UTCEchelonGraph re-scored
  33. 2026-09-19 13:04 UTCEchelonGraph re-scored
  34. 2026-09-18 19:28 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  35. 2026-09-16 21:30 UTCEchelonGraph re-scored
  36. 2026-09-16 14:08 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  37. 2026-09-11 23:32 UTCEchelonGraph re-scored
  38. 2026-09-11 14:53 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  39. 2026-09-09 00:38 UTCEchelonGraph re-scored
  40. 2026-09-08 22:01 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  41. 2026-09-05 19:05 UTCEchelonGraph re-scored
  42. 2026-09-05 15:31 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  43. 2026-09-04 19:33 UTCEchelonGraph re-scored
  44. 2026-09-04 05:07 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  45. 2026-08-30 20:25 UTCEchelonGraph re-scored
  46. 2026-08-30 01:22 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  47. 2026-08-29 20:54 UTCEchelonGraph re-scored
  48. 2026-08-28 21:42 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  49. 2026-08-28 20:42 UTCEchelonGraph re-scored
  50. 2026-08-28 19:47 UTCEchelonGraph re-scored
  51. 2026-08-28 00:32 UTCEchelonGraph re-scored
  52. 2026-08-27 23:24 UTCEchelonGraph re-scored
  53. 2026-08-27 20:26 UTCEchelonGraph re-scored
  54. 2026-08-27 20:15 UTCEchelonGraph re-scoredFirst assessed: 4.4 MEDIUM
  55. 2026-08-27 20:13 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-81523?
CVE-2026-81523 is a medium-severity vulnerability; its CVE record was published on August 27, 2026. 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…
When was the CVE record for CVE-2026-81523 published?
The CVE record for CVE-2026-81523 was published on August 27, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 17, 2026; the record at its source may have been updated since.
Is CVE-2026-81523 actively exploited?
CVE-2026-81523 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a <0.1% probability of exploitation in the next 30 days (below the 1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-81523?
CVE-2026-81523 has a CVSS base score of 4.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-81523?
A fix for CVE-2026-81523 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-81523

Explore →

Is Your Infrastructure Affected by CVE-2026-81523?

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

Book a Demo →Browse All CVEs