# CVE-2026-114645: Heap overflow via 32-bit length wrap of the URI username in Windows Kerberos auth message wrapping


- **Severity:** Medium 5.7 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 22 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-g9mw-2cwh-6hh9, UBUNTU-CVE-2026-114645

## What is CVE-2026-114645?

CVE-2026-114645 is a medium-severity vulnerability in MongoDB C Driver, published on 22 Oct 2026. 

### Official description

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.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2026-114645?


## How do I fix CVE-2026-114645?

No fix has been published for CVE-2026-114645 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-114645 being exploited?

There is no known exploitation of CVE-2026-114645 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-114645 and fix it if it is affected.

What it is: CVE-2026-114645 is a medium-severity vulnerability in MongoDB C Driver, published on 22 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-114645 in the wild and no public exploit code.

Affected product: MongoDB C Driver. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-114645/ (Markdown: https://insights.sbomify.com/CVE-2026-114645/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-114645
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-114645
- OSV: https://osv.dev/vulnerability/CVE-2026-114645

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-114645/
Summaries are generated and may contain mistakes; the official description above is the record.