MongoDB Ruby Driver unencrypted storage of fields in inherited models
- Exploited
- No known exploitation
- Fix
- See vendor advisory
- Who is exposed
- Not reported
Summary
In the MongoDB Ruby Driver, the Mongoid mapper skips its field-level encryption for some fields in models that use class inheritance, so those values are saved to the database in readable form without any error. An attacker who can reach the database over the network with a low-privilege account that has read access to the collections, but no access to the key store, can read those values without any user action.
Written by a model
Original 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.
What to do
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-126818 (Mongoid 9.1.1 incomplete CVE-2026-93764 fix stores descendant-only encrypted fields in plaintext), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-126818 (entry last updated 2026-11-17):
Affected:
- MongoDB Ruby Driver: versions 9.0.0, 9.0.1, 9.0.2, 9.0.3, 9.0.4, 9.0.5, 9.0.6, 9.0.7, 9.0.8, 9.0.9, 9.0.10, 9.0.11 and 3 more
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-126818 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126818 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://jira.mongodb.org/browse/MONGOID-6037
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-126818
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126818"}.Affected versions
- MongoDB Ruby Driver9.0.0, 9.0.1, 9.0.2, 9.0.3, 9.0.4, 9.0.5, 9.0.6, 9.0.7, 9.0.8, 9.0.9, 9.0.10, 9.0.11, 9.0.12, 9.1.0, 9.1.1
cve.now Index
- Exploitation0/40No signal
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch5/5No fixed version listed; see vendor advisory
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
- Would score about 34 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now4 days
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Public exploit activity
- EPSS: 0.10%
Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Link | jira.mongodb.org · browse/MONGOID-6037 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-126818 |
| Record | NVD · CVE-2026-126818 |
Questions about CVE-2026-126818
Is CVE-2026-126818 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-126818?
Ruby Driver: versions 9.0.0, 9.0.1, 9.0.2, 9.0.3, 9.0.4 and 10 more.
Source: cve.now feed data
Related
- CVE-2026-129924Credential exposure via unmasked connection string in driver parse-error messages for the Ruby driver
- CVE-2026-129925Authentication identity confusion via NUL-byte injection in SASL PLAIN credentials
- CVE-2026-88030GridFS data disclosure and deletion via query-operator injection in file IDs in the MongoDB Ruby Driver
- CVE-2026-126817Mongoid stores encrypted fields in plaintext when two models share a collection
- CVE-2026-129932Attacker able to redirect a Java driver client to a host they own, surviving TLS certificate verification, via an SRV parent-domain bypass
- CVE-2026-129938Attacker able to redirect a client's database traffic to a host they control via a comma in an SRV target, bypassing the SRV parent-domain…
No corrections so far. Something wrong on this page? Report an error.