VulnerabilityPublished 9 Nov 2026

CVE-2026-125119: Automattic mongoose · Improper Neutralization of Special Elements in Data Query Logic

Affects Automattic mongooseSource CVE Database V5

Compare

Not known to be exploited · CVSS 7.5 High · fixed in 9.11.4 : patch Automattic mongoose soon.

Data as of 9 Nov 2026, 22:49 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (GitHub_M)	CVSS 3.1	7.5

Patch: Available – fixed in 9.11.4, 8.24.7, 7.8.13 +1

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Automattic mongoose to 9.11.4, 8.24.7, 7.8.13 or 6.13.12.

Affected software

Product	Affected	Fixed in
Automatticmongoose	Affected >=9.0.0 <9.11.4	Fixed in 9.11.4
Automatticmongoose	Affected >=8.0.0 <8.24.7	Fixed in 8.24.7
Automatticmongoose	Affected >=7.0.0 <7.8.13	Fixed in 7.8.13
Automatticmongoose	Affected >=6.0.0 <6.13.12	Fixed in 6.13.12

AI-suggested

Upgrade Mongoose to version 6.13.12, 7.8.13, 8.24.7, or 9.11.4 or later, where this vulnerability is fixed. Avoid relying solely on connection-level sanitizeFilter configuration until patched. Global and per-query sanitizeFilter settings remain effective and can be used as interim mitigations. No other vendor advisories indicate additional mitigations or that no action is required.

Description

A vulnerability in Automattic's Mongoose library affects versions from 6.0.0 up to but not including 6.13.12, 7.8.13, 8.24.7, and 9.11.4. The issue involves improper neutralization of special elements in data query logic due to inconsistent handling of the sanitizeFilter option at the connection level. This can allow an attacker to bypass expected query sanitization when using connection-level configuration, potentially matching records without the correct literal values. The vulnerability is fixed in versions 6.13.12, 7.8.13, 8.24.7, and 9.11.4.

Impact

An attacker can exploit this flaw by injecting specially crafted query operators into filters when the sanitizeFilter option is enabled at the connection level, bypassing intended query sanitization. This can lead to unauthorized access to records, such as matching an account without the correct password. The vulnerability impacts confidentiality but does not affect integrity or availability. There are no known exploits in the wild at this time.

Summary

Mongoose versions 6.0.0 through versions prior to 6.13.12, 7.8.13, 8.24.7, and 9.11.4 improperly handle the sanitizeFilter option when set at the connection level via mongoose.connect() or createConnection(). While the connection's config reports sanitizeFilter as enabled, the query casting functions do not read this configuration from the connection, leading to unsanitized query selector objects. This inconsistency allows an attacker to craft query operators (e.g., in a password field) that bypass expected literal matching, potentially matching account records without the correct password. Global configuration via mongoose.set('sanitizeFilter') and per-query Model.find().sanitizeFilter() are unaffected. The issue is addressed in the fixed versions 6.13.12, 7.8.13, 8.24.7, and 9.11.4.

CWE-943Improper Neutralization of Special Elements in Data Query Logic (opens in a new tab)
Class weakness
The product generates a query intended to access or manipulate data in a data store such as a database, but it does not neutralize or incorrectly neutralizes special elements that can modify the intended logic of the query.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
OWASP ASVS 4.0.3
V1.5.1 (opens in a new tab)
Attack patterns
NoSQL Injection (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 9 Nov 2026, 22:49 UTC

WeaknessesCWE-943

Technical details

References

Community reviews

Related threats