What is CVE-2026-93762?

CVE-2026-93762 is Data deletion and attribute disclosure via field-name method injection in in-memory queries. The supplied enrichment data classifies it as Remote Code Exec mapped to CWE-470 CWE-470.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Active exploitation is not confirmed from current sources for CVE-2026-93762. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

No. CVE-2026-93762 is not listed in CISA KEV in the supplied enrichment data. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

Is there a public exploit?

A public PoC is not confirmed from current sources for CVE-2026-93762. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS, EDR process telemetry, host service logs where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2026-93762 using CVSS 9.8, EPSS 1%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

No public threat actor linkage is confirmed from current sources. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Prioritize based on EPSS, PoC availability, and external exposure. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

criticalRemote Code Exec

CVE-2026-93762

CVE-2026-93762 — Data deletion and attribute disclosure via field-name method injection in in-memory queries

Mongoid contains an unsafe reflection weakness in the query path used for embedded documents. An application that passes an externally supplied field name to certain in-memory query methods may allow an unauthenticated party to obtain unintended disclosure of stored document data and to permanently remove stored records.

Published Sep 18, 2026Updated Sep 24, 2026Sources: NVD, MongoDB Inc. (CNA), GitHub, GitHub Security Advisory, Red Hat (VEX)

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

chance of exploitation in 30 days

Affects

MongoDB Inc.

6 products listed

CVSS base

9.8

critical · 3 sources

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

None

none · proof-of-concept · active

Automatable

Yes

can an attacker script all four kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

The vendor's own words where we have them.

Upgrade Mongoid to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

Red Hat VEX · CVE-2026-93762

fixed0affected0not affected1

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Prioritize based on EPSS, PoC availability, and external exposure.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
MongoDB Inc.	Mongoid	9.1.0	Vulnerable
MongoDB Inc.	Mongoid	9.0.0 to <= 9.0.11	Vulnerable
MongoDB Inc.	Mongoid	8.1.0 to <= 8.1.12	Vulnerable
MongoDB Inc.	Mongoid	8.0.0 to <= 8.0.12	Vulnerable
MongoDB Inc.	Mongoid	7.6.0 to <= 7.6.1	Vulnerable
MongoDB Inc.	Mongoid	7.5.0 to <= 7.5.4	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

High

Confidentiality

High

Integrity

High

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Network

Privileges Req

None

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
9.8	CVSS 3.1	critical	3.9	5.9	mongodb.com (CNA), MongoDB Inc. (CNA), GHSA
9.2	CVSS 4.0	critical	—	—	MongoDB Inc. (CNA)
8.1	CVSS 3.1	high	—	—	Red Hat (VEX)

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Weakness & attack patterns

CWE-470

Inferred from the weakness class — not observed against this CVE.

CAPEC-242 · Code InjectionCAPEC-35 · Leverage Executable Code in Non-Executable Files

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Prioritize edge telemetry for network-reachable Mongoid.

web/proxy/WAF logsapplication logsnetwork IDS/IPSEDR process telemetryhost service logs

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 9.8 (AV:N)
Sep 24, 2026 · NVD
Initial · CVE published
Sep 18, 2026 · NVD
Added · GHSA-36hj-r7fq-q38m published (critical)
Sep 18, 2026 · GitHub Security Advisory

References

5 on the record

jira.mongodb.org/browse/MONGOID-5973
Permissions Required
nvd.nist.gov/vuln/detail/CVE-2026-93762
NVD
github.com/advisories/GHSA-36hj-r7fq-q38m
Exploit, Third Party Advisory
access.redhat.com/security/cve/CVE-2026-93762
Vendor Advisory
www.cve.org/CVERecord?id=CVE-2026-93762
Vendor Advisory

Elsewhere on this site

MongoDB Inc.every CVE for this vendor
Remote Code Execsame class
CWE-470other pages naming this weakness

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 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 record1

What should defenders know first?

CVE-2026-93762 is Data deletion and attribute disclosure via field-name method injection in in-memory queries, a critical vulnerability affecting Mongoid from MongoDB Inc.. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-93762. Public exploit evidence is: A public PoC is not confirmed from current sources for CVE-2026-93762. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 9.8 describes technical severity, while EPSS 1% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.