# CVE-2026-120813: Plaintext storage of encrypted fields via duplicate keys in client-side encryption schema parsing


- **Severity:** High 8.2 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/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-9w78-m6x6-2jpp

## What is CVE-2026-120813?

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

### Official description

An issue in MongoDB Server's client-side field-level encryption (CSFLE) schema processing component allows encryption metadata to be silently dropped during schema parsing under certain conditions. A party who can deliver a specially crafted schema to a user's CSFLE client may cause sensitive data intended for encryption to be stored in plaintext, bypassing confidentiality protections. Exploitation requires the ability to deliver the malicious schema to the user's client, such as through a man-in-the-middle position or an untrusted server.

Weakness: CWE-436 (Interpretation Conflict)

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


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

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

## Is CVE-2026-120813 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-120813 is a high-severity vulnerability in MongoDB Server, published on 10 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-120813 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-120813/ (Markdown: https://insights.sbomify.com/CVE-2026-120813/index.md)
```

## Sources

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

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