# CVE-2026-120804: Credential-handle retention via missing flag set in Windows Kerberos auth handler


- **Severity:** High 8.2 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 10 Nov 2026
- **Updated:** 13 Nov 2026
- **Also known as:** GHSA-8mq6-8rqq-65vp

## What is CVE-2026-120804?

CVE-2026-120804 is a high-severity vulnerability in MongoDB Server, published on 10 Nov 2026. 

### Official description

A flaw exists in the server-side SSPI Kerberos authentication handler on Windows Enterprise builds of MongoDB. When processing certain authentication requests, the server fails to properly release an underlying system resource due to an internal tracking error. An unauthenticated user can trigger this by repeatedly sending authentication requests using the Kerberos mechanism, eventually exhausting available resources and causing all subsequent Kerberos authentication attempts to fail. Server restart is required to recover.

Weakness: CWE-772 (Missing Release of Resource after Effective Lifetime)

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


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

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

## Is CVE-2026-120804 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-120804 is a high-severity vulnerability in MongoDB Server, published on 10 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-120804 in the wild and no public exploit code.

Affected product: MongoDB Server. 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-120804/ (Markdown: https://insights.sbomify.com/CVE-2026-120804/index.md)
```

## Sources

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

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