Mongoose is a MongoDB object modeling tool designed to work in an asynchronous environment. From 6.0.0 until 6.13.12, 7.8.13, 8.24.7, and 9.11.4, Mongoose stores the connection-level sanitizeFilter option in Connection.config, but Query.prototype._castConditions() and query casting check other option locations and do not read that configuration. An application that enables sanitizeFilter through mongoose.connect() or createConnection() and passes an attacker-controlled object into a query filter therefore receives a connection that reports the defense as enabled while query selector objects remain unsanitized. A crafted password value using a query operator can match an account record without the expected literal password, while global configuration through mongoose.set('sanitizeFilter') and per-query Model.find().sanitizeFilter() remain unaffected. This issue is fixed in versions 6.13.12, 7.8.13, 8.24.7, and 9.11.4.
CVE-2026-125119
“—” beside the score: it is equal to the CVSS score beside it.
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-11-10. A secondary CVSS source baseline 7.5; sources differ by 0.0.
Also known asEUVD-2026-120502 (ENISA EUVD) · GHSA-gg4r-jv3p-qx3c (GitHub Security Advisories)Source: ENISA EUVD
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.5
- EG Score
- 7.5HIGHhigh confidence
- EG Risk
- 49EG Risk 49/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity75% × 45%Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.5% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability100% × 15%CISA's SSVC Automatable value: yes (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 0.5%
- EPSS %ILE
- 45th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.
- EG Severity
- 7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
November 9, 2026
Last Modified
November 12, 2026
Advisory Details (7)
Auto-updated Nov 9, 20269.11.4
Patch available: Automattic/mongoose 9.11.4
https://github.com/Automattic/mongoose/releases/tag/9.11.48.24.7
Patch available: Automattic/mongoose 8.24.7
https://github.com/Automattic/mongoose/releases/tag/8.24.7commit b8970c25998c (Automattic/mongoose)
Fix landed in Automattic/mongoose commit b8970c25998c — awaiting tagged release
https://github.com/Automattic/mongoose/commit/b8970c25998c23fbccd17f76c0398b902ff4911dcommit 83eda6af1489 (Automattic/mongoose)
Patch available: Automattic/mongoose 8.24.7 (contains commit 83eda6af1489)
https://github.com/Automattic/mongoose/commit/83eda6af1489e9ef60bb8eee8cf9ee005771b9d5commit 4f4f9a79f860 (Automattic/mongoose)
Fix landed in Automattic/mongoose commit 4f4f9a79f860 — awaiting tagged release
https://github.com/Automattic/mongoose/commit/4f4f9a79f860786a54133bee2c9af967ec691491commit 4bb659478be2 (Automattic/mongoose)
Patch available: Automattic/mongoose 9.11.4 (contains commit 4bb659478be2)
https://github.com/Automattic/mongoose/commit/4bb659478be2f30655a7bdd78bc251bdf111cd29Connection-level sanitizeFilter not applied · Advisory · Automattic/mongoose · GitHub
https://github.com/Automattic/mongoose/security/advisories/GHSA-gg4r-jv3p-qx3cVendor Advisories for CVE-2026-125119(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(4)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| npm | mongoose @ 6.13.12 (fixes >= 6.0.0, < 6.13.12) | — | ghsa |
| npm | mongoose @ 7.8.13 (fixes >= 7.0.0, < 7.8.13) | — | ghsa |
| npm | mongoose @ 8.24.7 (fixes >= 8.0.0, < 8.24.7) | — | ghsa |
| npm | mongoose @ 9.11.4 (fixes >= 9.0.0, < 9.11.4) | — | ghsa |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| mongoose | — |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 8× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.
- 2026-11-12 19:29 UTCEchelonGraph re-scored
- 2026-11-12 19:29 UTCGHSA enrichmentGHSA-gg4r-jv3p-qx3c · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-11-12 18:48 UTCEchelonGraph re-scored
- 2026-11-12 18:48 UTCGHSA enrichmentGHSA-gg4r-jv3p-qx3c · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.5% · 45th percentile
- 2026-11-11 16:38 UTCEPSS rescoreEPSS 0.5% · 45th percentile
- 2026-11-10 23:23 UTCEchelonGraph re-scored
- 2026-11-10 23:23 UTCGHSA enrichmentGHSA-gg4r-jv3p-qx3c · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-11-10 16:42 UTCEPSS rescoreEPSS 0.5% · 45th percentile
- 2026-11-09 23:00 UTCENISA EUVD ID recordedEUVD-2026-120502 · Source: ENISA EUVD
- 2026-11-09 22:40 UTCEchelonGraph re-scoredFirst assessed: 7.5 HIGH
- 2026-11-09 22:39 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Same product
10 shownnpm:mongoose
- CVE-2023-3696NVD 9.8EG 10.0CRITICAL
- CVE-2026-125120EG 9.8CRITICAL
- CVE-2024-53900NVD 9.1EG 9.8EPSS p91CRITICAL
- CVE-2022-2564EG 9.8EPSS p98CRITICAL
- CVE-2019-17426EG 9.1CRITICAL
- CVE-2025-23061EG 9.0EPSS p94CRITICAL
- CVE-2026-125117EG 8.2HIGH
- CVE-2026-42334EG 7.5HIGH
- CVE-2026-125118EG 6.5MEDIUM
- CVE-2026-73562EG 6.5MEDIUM
Frequently asked(5)
What is CVE-2026-125119?
When was the CVE record for CVE-2026-125119 published?
Is CVE-2026-125119 actively exploited?
What is the CVSS score of CVE-2026-125119?
How do I remediate CVE-2026-125119?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-125119
Is Your Infrastructure Affected by CVE-2026-125119?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.