# CVE-2026-120807: Privilege escalation via fail-open user lookup in X.509 cluster-membership guard


- **Severity:** High 7.5 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:N/VC:H/VI:H/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-6c5q-2vf6-gqj4

## What is CVE-2026-120807?

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

### Official description

A flaw in MongoDB’s X.509 cluster-membership authentication guard could allow a holder of a cluster-member certificate to gain elevated internal privileges when a specific deployment configuration is in use. An internal check, which prevents a certificate recognized as a cluster member from also being treated as a regular user, does not correctly distinguish between certain error conditions encountered during user lookup. Under certain timing conditions, this can cause the check to be bypassed, granting the connection full internal system privileges. Triggering this issue requires possession of a valid cluster-member TLS certificate, non-default X.509 cluster authentication configuration, and specific conditions during the user cache lookup process.

Weakness: CWE-754 (Improper Check for Unusual or Exceptional Conditions)

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


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

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

## Is CVE-2026-120807 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120807 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-120807 is a high-severity vulnerability in MongoDB Server, published on 10 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120807 exists.

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-120807/ (Markdown: https://insights.sbomify.com/CVE-2026-120807/index.md)
```

## Sources

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

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