CVE-2026-81517

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

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

An unauthenticated party able to reach the port of a MongoDB Connector for BI (mongosqld) instance may generate enough routine connection log activity to exhaust the storage backing the configured log path. When a log write or log rotation operation subsequently fails, the resulting error is not handled and the shared mongosqld process ends, ending service for all connected SQL clients. The process continues to end on startup until an operator restores available storage, and the diagnostic message explaining the condition is not recorded.

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
49(Track)
EG Risk 49/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
Severity75% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
18%
KEV
Not listed

Published

August 28, 2026

Last Modified

September 1, 2026

Advisory Details (1)

Auto-updated Aug 28, 2026
No patch confirmed yet.
generic

Release Notes for MongoDB Connector for BI - BI Connector - MongoDB Docs

https://www.mongodb.com/docs/bi-connector/current/release-notes/

Vendor Advisories for CVE-2026-81517(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 24× in last 7d / 83× 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-19 12:05 UTCGHSA enrichment
  2. 2026-09-18 23:00 UTCEG score recompute
  3. 2026-09-18 23:00 UTCGHSA enrichment
  4. 2026-09-18 19:28 UTCEPSS rescore
  5. 2026-09-18 09:55 UTCGHSA enrichment
  6. 2026-09-17 20:50 UTCEG score recompute
  7. 2026-09-17 20:50 UTCGHSA enrichment
  8. 2026-09-17 05:24 UTCGHSA enrichment
  9. 2026-09-16 16:18 UTCEG score recompute
  10. 2026-09-16 16:18 UTCGHSA enrichment
  11. 2026-09-16 14:08 UTCEPSS rescore
  12. 2026-09-16 05:15 UTCEPSS rescore
  13. 2026-09-16 03:11 UTCGHSA enrichment
  14. 2026-09-15 14:06 UTCEG score recompute
  15. 2026-09-15 14:06 UTCGHSA enrichment
  16. 2026-09-15 03:12 UTCEPSS rescore
  17. 2026-09-15 03:12 UTCEPSS rescore
  18. 2026-09-15 01:01 UTCGHSA enrichment
  19. 2026-09-14 11:56 UTCGHSA enrichment
  20. 2026-09-13 22:51 UTCEG score recompute
  21. 2026-09-13 22:51 UTCGHSA enrichment
  22. 2026-09-13 09:46 UTCGHSA enrichment
  23. 2026-09-12 20:41 UTCEG score recompute
  24. 2026-09-12 20:41 UTCGHSA enrichment
  25. 2026-09-12 07:36 UTCGHSA enrichment
Show 58 more
  1. 2026-09-11 18:29 UTCEG score recompute
  2. 2026-09-11 18:29 UTCGHSA enrichment
  3. 2026-09-11 14:53 UTCEPSS rescore
  4. 2026-09-11 14:53 UTCEPSS rescore
  5. 2026-09-11 05:23 UTCGHSA enrichment
  6. 2026-09-10 16:18 UTCEG score recompute
  7. 2026-09-10 16:18 UTCGHSA enrichment
  8. 2026-09-10 02:52 UTCGHSA enrichment
  9. 2026-09-09 13:47 UTCGHSA enrichment
  10. 2026-09-09 00:26 UTCEG score recompute
  11. 2026-09-09 00:26 UTCGHSA enrichment
  12. 2026-09-08 22:01 UTCEPSS rescore
  13. 2026-09-08 10:30 UTCGHSA enrichment
  14. 2026-09-07 21:20 UTCEG score recompute
  15. 2026-09-07 21:20 UTCGHSA enrichment
  16. 2026-09-07 08:14 UTCGHSA enrichment
  17. 2026-09-06 19:09 UTCEG score recompute
  18. 2026-09-06 19:09 UTCGHSA enrichment
  19. 2026-09-06 13:48 UTCEPSS rescore
  20. 2026-09-06 05:59 UTCGHSA enrichment
  21. 2026-09-05 16:53 UTCEG score recompute
  22. 2026-09-05 16:53 UTCGHSA enrichment
  23. 2026-09-05 15:31 UTCEPSS rescore
  24. 2026-09-05 03:47 UTCGHSA enrichment
  25. 2026-09-04 14:41 UTCEG score recompute
  26. 2026-09-04 14:41 UTCGHSA enrichment
  27. 2026-09-04 05:07 UTCEPSS rescore
  28. 2026-09-04 01:36 UTCGHSA enrichment
  29. 2026-09-03 12:29 UTCGHSA enrichment
  30. 2026-09-02 23:22 UTCEG score recompute
  31. 2026-09-02 23:22 UTCGHSA enrichment
  32. 2026-09-02 14:12 UTCEPSS rescore
  33. 2026-09-02 10:16 UTCGHSA enrichment
  34. 2026-09-01 21:10 UTCEG score recompute
  35. 2026-09-01 21:10 UTCGHSA enrichment
  36. 2026-09-01 13:54 UTCEPSS rescore
  37. 2026-09-01 08:35 UTCEG score recompute
  38. 2026-09-01 08:35 UTCGHSA enrichment
  39. 2026-09-01 04:40 UTCEPSS rescore
  40. 2026-09-01 04:40 UTCEPSS rescore
  41. 2026-08-31 19:30 UTCEG score recompute
  42. 2026-08-31 19:30 UTCGHSA enrichment
  43. 2026-08-31 18:56 UTCEG score recompute
  44. 2026-08-31 18:56 UTCGHSA enrichment
  45. 2026-08-31 16:45 UTCGHSA enrichment
  46. 2026-08-31 03:08 UTCEG score recompute
  47. 2026-08-31 03:08 UTCGHSA enrichment
  48. 2026-08-30 19:18 UTCEPSS rescore
  49. 2026-08-30 19:17 UTCEPSS rescore
  50. 2026-08-30 14:01 UTCEG score recompute
  51. 2026-08-30 14:01 UTCGHSA enrichment
  52. 2026-08-30 01:22 UTCEPSS rescore
  53. 2026-08-30 00:56 UTCGHSA enrichment
  54. 2026-08-29 11:51 UTCEG score recompute
  55. 2026-08-29 11:51 UTCGHSA enrichment
  56. 2026-08-28 22:43 UTCEG score recompute
  57. 2026-08-28 22:02 UTCEG score recompute
  58. 2026-08-28 21:59 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-81517?
CVE-2026-81517 is a high vulnerability published on August 28, 2026. An unauthenticated party able to reach the port of a MongoDB Connector for BI (mongosqld) instance may generate enough routine connection log activity to exhaust the storage backing the configured log path. When a log write or log rotation operation subsequently fails, the resulting error is not…
When was CVE-2026-81517 disclosed?
CVE-2026-81517 was first published in the National Vulnerability Database on August 28, 2026, with the most recent update on September 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-81517 actively exploited?
CVE-2026-81517 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.6% of all scored CVEs.
What is the CVSS score of CVE-2026-81517?
CVE-2026-81517 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-81517?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-81517, 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-81517

Explore →

Is Your Infrastructure Affected by CVE-2026-81517?

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

Start Free Scan →Browse All CVEs