VulnerabilityPublished 10 Nov 2026

CVE-2026-125119: Mongoose · Connection-level sanitizeFilter not applied

Affects mongooseSource GCVE Database

Compare

Authoritative record:CVE-2026-125119· High 7.5

Not known to be exploited · CVSS 7.5 High : upgrade to 6.13.12 soon.

Data as of 10 Nov 2026, 23:24 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

EPSS: 0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 6.13.12, 7.8.13, 8.24.7 +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 10 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 to a fixed release listed under Affected software.

Affected software

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

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available in Mongoose versions 6.13.12, 7.8.13, 8.24.7, and 9.11.4 that fixes the sanitizeFilter application at the connection level. Users should upgrade to these fixed versions or later. Alternatively, users can mitigate the issue by setting sanitizeFilter globally using mongoose.set('sanitizeFilter') or on individual queries using Model.find().sanitizeFilter(), which are not affected by this vulnerability.

Description

Mongoose versions from 6.0.0 up to but not including 6.13.12, 7.0.0 up to 7.8.13, 8.0.0 up to 8.24.7, and 9.0.0 up to 9.11.4 have a vulnerability where the connection-level sanitizeFilter option is not applied. This option is intended to prevent query selector injection by wrapping operator objects in filters to match them literally. Due to a coding mismatch, the sanitizeFilter setting is reported as enabled but does not actually sanitize queries, allowing attackers to bypass this protection. The vulnerability does not affect users who set sanitizeFilter globally or on specific queries. A fix is available in later versions.

Impact

The vulnerability allows an attacker to bypass the intended query selector injection protection when the sanitizeFilter option is set only at the connection level. This can lead to unauthorized data retrieval, such as accessing user records without proper password verification. The impact is high confidentiality loss (C:H) with no integrity or availability impact. Applications relying solely on connection-level sanitizeFilter are vulnerable, while those using global or per-query sanitizeFilter are not affected.

Summary

The sanitizeFilter option in Mongoose is designed to prevent query selector injection by wrapping operator objects such as {$ne: null} in filters to ensure they are matched literally. However, when set at the connection level via mongoose.connect() or createConnection(uri, { sanitizeFilter: true }), the option is stored in Connection.config but the query casting logic checks Connection.options instead, causing the sanitizeFilter defense to never run. This flaw exists in Mongoose versions starting from 6.0.0 through 9.11.2. An attacker can exploit this by injecting operator objects into filters, for example, using {password: {$ne: null}} to bypass password checks and retrieve protected records. The vulnerability affects only connection-level sanitizeFilter usage; global or per-query sanitizeFilter settings remain effective. Fixed versions include 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 10 Nov 2026, 22:32 UTC

WeaknessesCWE-943

Technical details

References

Community reviews

Related threats