CVE-2026-81530

MEDIUMPre-NVD 5.65.6
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 5.6 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
5.6EG
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: 5.6Exploit: None knownExposed services: Not assessed

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

A weakness in the client-side encryption configuration surface of the MongoDB C# Driver causes sensitive key-management credential material supplied by the application to be reproduced verbatim in the driver's human-readable diagnostic representation of its client settings, instead of being masked as other secret fields are. A party able to read the application's logs, diagnostic output, or a process memory dump may thereby recover the plaintext credentials and use them to decrypt protected field data.

CVSS v3
5.6
EG Score
5.6MEDIUMmedium confidence
EG Risk
25
EG Risk 25/100

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 (value × EchelonGraph’s weight)
Severity56% × 45%
The EG Score, 5.6 of 10.
Exploitation<0.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: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
<0.1%
EPSS %ILE
below the 1st
KEV
Not listed

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

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

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.

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 29, 2026

Advisory Details (1)

Auto-updated Aug 27, 2026
No fix on record yet.
Web page

NuGet Gallery | MongoDB.Driver 3.11.1

https://www.nuget.org/packages/MongoDB.Driver/3.11.1

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 36× 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 it from the CNA feed. 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). 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 51 is merged into the row it repeats.

  1. 2026-10-11 19:20 UTCEG score recompute
  2. 2026-10-11 16:37 UTCEG score recompute
  3. 2026-10-11 13:55 UTCEG score recompute
  4. 2026-10-11 13:49 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  5. 2026-10-10 20:00 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  6. 2026-10-10 02:07 UTCEG score recompute
  7. 2026-10-09 20:07 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  8. 2026-10-09 02:56 UTCEG score recompute
  9. 2026-10-08 17:13 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  10. 2026-10-08 01:14 UTCEG score recompute
  11. 2026-10-07 23:48 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  12. 2026-10-06 17:57 UTCEG score recompute
  13. 2026-10-06 15:18 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  14. 2026-10-05 18:54 UTCEG score recompute
  15. 2026-10-04 23:22 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  16. 2026-10-03 19:21 UTCEG score recompute
  17. 2026-10-03 14:26 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  18. 2026-10-02 18:55 UTCEG score recompute
  19. 2026-10-02 17:57 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  20. 2026-10-01 19:52 UTCEG score recompute
  21. 2026-10-01 19:50 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  22. 2026-09-30 19:54 UTCEG score recompute
  23. 2026-09-30 15:04 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  24. 2026-09-29 15:33 UTCEG score recompute
  25. 2026-09-28 16:30 UTCEG score recompute
Show 25 more
  1. 2026-09-28 13:52 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  2. 2026-09-27 17:27 UTCEG score recompute
  3. 2026-09-27 13:48 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  4. 2026-09-26 18:24 UTCEG score recompute
  5. 2026-09-26 15:59 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  6. 2026-09-24 20:07 UTCEG score recompute
  7. 2026-09-24 14:04 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  8. 2026-09-23 21:04 UTCEG score recompute
  9. 2026-09-23 17:54 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  10. 2026-09-17 03:43 UTCEG score recompute
  11. 2026-09-16 14:08 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  12. 2026-09-12 07:46 UTCEG score recompute
  13. 2026-09-11 14:53 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  14. 2026-09-06 13:12 UTCEG score recompute
  15. 2026-09-05 15:31 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  16. 2026-09-05 14:09 UTCEG score recompute
  17. 2026-08-29 20:25 UTCEG score recompute
  18. 2026-08-28 21:42 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  19. 2026-08-28 20:41 UTCEG score recompute
  20. 2026-08-28 19:46 UTCEG score recompute
  21. 2026-08-28 00:32 UTCEG score recompute
  22. 2026-08-27 23:24 UTCEG score recompute
  23. 2026-08-27 20:26 UTCEG score recompute
  24. 2026-08-27 20:14 UTCEG score recomputeFirst assessed: 5.6 MEDIUM
  25. 2026-08-27 20:13 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-81530?
CVE-2026-81530 is a medium-severity vulnerability; its CVE record was published on August 27, 2026. A weakness in the client-side encryption configuration surface of the MongoDB C# Driver causes sensitive key-management credential material supplied by the application to be reproduced verbatim in the driver's human-readable diagnostic representation of its client settings, instead of being masked…
When was the CVE record for CVE-2026-81530 published?
The CVE record for CVE-2026-81530 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 29, 2026; the record at its source may have been updated since.
Is CVE-2026-81530 actively exploited?
CVE-2026-81530 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-81530?
CVE-2026-81530 has a CVSS base score of 5.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-81530?
No fix for CVE-2026-81530 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-81530

Explore →

Is Your Infrastructure Affected by CVE-2026-81530?

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

Book a Demo →Browse All CVEs