CVE-2026-114650 — Plaintext exposure of encrypted fields via ANSI code-page corruption of database name
A flaw in the client-side encryption support of the MongoDB .NET/C# driver can cause data designated for client-side field-level encryption to be written without encryption. Under certain platform text-encoding configurations, an internal name conversion loses information, so the encryption layer fails to associate the operation with its configured encryption rules and the operation proceeds without an error being raised. An application user with the ability to write data through an affected application can therefore have sensitive fields persisted in plaintext, defeating the confidentiality guarantee that client-side encryption is intended to provide. No integrity or availability impact was observed.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.1% (30-day exploitation probability)+0
- Technical severity (medium)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Mongodb C Driver, Mongodb MongoDB.Libmongocrypt NuGet package).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Mongodb | C Driver | ≥ 2.10.0 and < 3.13.0 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Mongodb | MongoDB.Libmongocrypt NuGet package | ≥ 1.0.0 and ≤ 1.12.0 | Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 6.9 | CVSS 4.0 | Medium | — | — | cna@mongodb.com via NIST National Vulnerability Database |
| 6.9 | CVSS 4.0 | Medium | — | — | mongodb via CVE Program (cve.org) e CISA ADP |
| 5.9 | CVSS 3.1 | Medium | 1.4 | 4.0 | cna@mongodb.com via NIST National Vulnerability Database |
| 5.9 | CVSS 3.1 | Medium | — | — | mongodb via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N (score shown at the top: cna@mongodb.com) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 23, 2026 → Oct 27, 2026 · 5 reading(s) · max 0.11%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
Timeline
What happened to this CVE, newest first.
- 2026
- Source status changed · Received → Awaiting Analysis
- Affected products added · mongodb/mongodb.libmongocrypt nuget package
- Affected products added · mongodb/c# driver
- Record published
- CVSS changed · 5.9
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 22, 2026 – Oct 22, 2026
- 1× Official description updated · Oct 22, 2026 – Oct 22, 2026
References
3 on the record
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2026-114651 Cross-document data leak via malformed BSON array parsing in reused thread buffer 5d
- Medium CVE-2026-114652 Update operator injection via single-element list rewriting in the update builder 5d
- Medium CVE-2026-114653 Silent client-side encryption bypass via unescaped field-name regex in CSFLE schema builder 5d
- Medium CVE-2026-114654 BSON output corruption via out-of-range binary subtype bypassing UUID and OldBinary guards 5d
- High CVE-2026-114648 NoSQL injection via dot and dollar characters in LINQ filter field names and dictionary keys 5d
- Medium CVE-2026-114647 NoSQL operator injection via unvalidated replacement document in findOneAndReplace 5d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-114650 is "Plaintext exposure of encrypted fields via ANSI code-page corruption of database name", rated Medium. It affects C Driver (Mongodb); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.9 describes technical severity. EPSS 0.11% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.