# CVE-2026-126818: Mongoid 9.1.1 incomplete CVE-2026-93764 fix stores descendant-only encrypted fields in plaintext


- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 13 Nov 2026
- **Updated:** 13 Nov 2026
- **Also known as:** GHSA-q5w2-57qp-493f

## What is CVE-2026-126818?

CVE-2026-126818 is a high-severity vulnerability in MongoDB Ruby Driver, published on 13 Nov 2026. 

### Official description

A Ruby object-document mapper does not apply its automatic field-level encryption configuration to certain fields when the data model uses class inheritance. Values the application designated for encryption are written to the database in readable form without any error or warning. A database account holding only read access to the application's collections, and no access to the encryption key store, may obtain those values.

Weakness: CWE-311 (Missing Encryption of Sensitive Data)

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


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

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

## Is CVE-2026-126818 being exploited?

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

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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