CVE-2026-114645: Heap overflow via 32-bit length wrap of the URI username in Windows Kerberos auth message wrapping
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-11 15:49 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
A 32-bit integer wraparound in the MongoDB C Driver’s Windows-only Kerberos/SSPI authentication code can cause an undersized heap buffer to be allocated when an excessively long credential value is supplied in the client’s connection configuration. A party able to control that client-side configuration, in conjunction with the affected authentication mechanism, can cause the driver to write outside the bounds of the allocated buffer. This may result in corruption of client process memory and denial of service of the client application. The issue affects only client builds compiled with the Windows-native authentication backend.
Description quoted from the CVE record (assigned by mongodb, published 2026-10-22).
Weakness: CWE-190: Integer Overflow or Wraparound
How it can be exploited
Exploitable with local access with high attack complexity only when specific conditions are present needing high privileges and no user interaction. Impact: confidentiality low, integrity low, availability high. CVSS:4.0/AV:L/AC:H/AT:P/PR:H/UI:N/VC:L/VI:L/VA:H/SC:N/SI:N/SA:N
CISA assessment (SSVC): CISA has no evidence of exploitation. Automatable: no. Technical impact: partial.
Public exploit evidence (Exploit Observer)
Exploit Observer has no public exploit code naming this CVE. Check Exploit Observer for anything new.
Live scores
- EPSS
- 0.002
low predicted chance of attack - VEDAS
- 0.056
little exploit evidence - On CISA KEV
- Not listed
- Detection rule
- No public rule yet
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| MongoDB C Driver | from 1.6.0 before 1.30.14 from 2.0.0 before 2.5.7 | Not stated |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
How to fix it
Fixed versions stated in the CVE record: 1.30.14, 2.5.7.
How to detect it
There is no open VEDAS detection rule for this bug yet. It is listed on the detection gaps page if CISA has confirmed attacks.
Advisories on this CVE
References
Other references
- https://jira.mongodb.org/browse/CDRIVER-6421
- https://github.com/mongodb/mongo-c-driver/releases/tag/1.30.14
- https://github.com/mongodb/mongo-c-driver/releases/tag/2.5.7
- https://github.com/mongodb/mongo-c-driver/security/advisories/GHSA-g9mw-2cwh-6hh9
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.
Supporting partners
