An application using the MongoDB BI Connector ODBC Driver may encounter a memory-safety issue when a submitted SQL statement contains an unusually long run of digits following a LIMIT clause. The issue occurs only on connections where the driver's optional prefetch setting is enabled, and stems from the driver copying the digit sequence into a fixed-size internal buffer without checking its length. A user able to influence the numeric portion of a LIMIT clause could cause the hosting application process to terminate unexpectedly or corrupt adjacent memory in that process.
CVE-2026-81533
Score 7.1 from GitHub Security Advisory published 2026-08-29. a secondary CVSS source baseline 7.1; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.1
- EG Score
- 7.1(high)
- EG Risk
- 36(Track)EG Risk 36/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 computedSeverity71% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 10%
- KEV
- Not listed
Published
August 28, 2026
Last Modified
August 28, 2026
Advisory Details (1)
Auto-updated Aug 28, 2026Releases · mongodb/mongo-bi-connector-odbc-driver · GitHub
https://github.com/mongodb/mongo-bi-connector-odbc-driver/releasesVendor Advisories for CVE-2026-81533(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 7× in last 7d / 7× 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 22:24 UTCGHSA enrichment
- 2026-08-29 10:34 UTCEG score recompute
- 2026-08-29 10:34 UTCGHSA enrichment
- 2026-08-28 22:43 UTCEG score recompute
- 2026-08-28 22:02 UTCEG score recompute
- 2026-08-28 21:59 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-121
Frequently asked(5)
What is CVE-2026-81533?
When was CVE-2026-81533 disclosed?
Is CVE-2026-81533 actively exploited?
What is the CVSS score of CVE-2026-81533?
How do I remediate CVE-2026-81533?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-81533
Is Your Infrastructure Affected by CVE-2026-81533?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.