CVE-2026-125120

CRITICALPre-NVD 9.89.8
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-11-10. A secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-120503 (ENISA EUVD) · GHSA-pcrw-h46h-c93h (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Mongoose is a MongoDB object modeling tool designed to work in an asynchronous environment. Prior to 6.13.11, 7.8.12, 8.24.3, and 9.9.2, Mongoose countDocuments() does not apply the configured sanitizeFilter query selector injection defense. An application that enables sanitizeFilter and passes attacker-controlled filter values to countDocuments() can therefore process query operator objects as operators rather than literal values, causing the count to include documents that should not match and potentially undermining authorization or application logic based on that count. This issue is fixed in versions 6.13.11, 7.8.12, 8.24.3, and 9.9.2.

CVSS v3
9.8
EG Score
9.8CRITICALhigh confidence
EG Risk
44
EG Risk 44/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)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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.
EPSS PROB
0.6%
EPSS %ILE
47th
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 (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.6% 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; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade 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; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (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 13, 2026

Advisory Details (9)

Auto-updated Nov 9, 2026
Patch available. Sources: github, github_commit, github_release.
GitHub release Patch Available

9.9.2

Patch available: Automattic/mongoose 9.9.2

https://github.com/Automattic/mongoose/releases/tag/9.9.2
GitHub release Patch Available

8.24.3

Patch available: Automattic/mongoose 8.24.3

https://github.com/Automattic/mongoose/releases/tag/8.24.3
GitHub release Patch Available

7.8.12

Patch available: Automattic/mongoose 7.8.12

https://github.com/Automattic/mongoose/releases/tag/7.8.12
GitHub release Patch Available

6.13.11

Patch available: Automattic/mongoose 6.13.11

https://github.com/Automattic/mongoose/releases/tag/6.13.11
GitHub commit Patch Available

commit b5003d3915db (Automattic/mongoose)

Patch available: Automattic/mongoose 9.9.2 (contains commit b5003d3915db)

https://github.com/Automattic/mongoose/commit/b5003d3915db1cf9209c38a4b93cf3a92cddd710
GitHub commit Patch Available

commit b1df045aab07 (Automattic/mongoose)

Patch available: Automattic/mongoose 6.13.11 (contains commit b1df045aab07)

https://github.com/Automattic/mongoose/commit/b1df045aab076b740fdaec14a15a44c694b85b7d
GitHub commit Patch Available

commit 8b10d5760bb1 (Automattic/mongoose)

Patch available: Automattic/mongoose 8.24.3 (contains commit 8b10d5760bb1)

https://github.com/Automattic/mongoose/commit/8b10d5760bb181f5bf5d01495cde161c8aed0557
GitHub commit Patch Available

commit 7e912af3fac5 (Automattic/mongoose)

Patch available: Automattic/mongoose 7.8.12 (contains commit 7e912af3fac5)

https://github.com/Automattic/mongoose/commit/7e912af3fac52cb0eea4cd71e24d65318916831a
GitHub advisoryMentions a patch (unverified)

sanitizeFilter not applied on countDocuments · Advisory · Automattic/mongoose · GitHub

https://github.com/Automattic/mongoose/security/advisories/GHSA-pcrw-h46h-c93h

Vendor Advisories for CVE-2026-125120(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 / EcosystemFix (by version range) / PatchReleasedSource
npmmongoose @ 6.13.11 (fixes < 6.13.11)—ghsa
npmmongoose @ 7.8.12 (fixes >= 7.0.0, < 7.8.12)—ghsa
npmmongoose @ 8.24.3 (fixes >= 8.0.0, < 8.24.3)—ghsa
npmmongoose @ 9.9.2 (fixes >= 9.0.0, < 9.9.2)—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)
PackageVulnerable rangeFix by version rangeDependents
mongoose—
  • every version up to 6.13.11: fixed in 6.13.11
  • 7.0.0 up to 7.8.12: fixed in 7.8.12
  • 8.0.0 up to 8.24.3: fixed in 8.24.3
  • 9.0.0 up to 9.9.2: fixed in 9.9.2
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 11× 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.

  1. 2026-11-13 16:50 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  2. 2026-11-13 14:29 UTCEchelonGraph re-scored
  3. 2026-11-13 14:29 UTCGHSA enrichmentGHSA-pcrw-h46h-c93h · GitHub severity CRITICAL · GitHub CVSS 9.8
  4. 2026-11-13 13:50 UTCEchelonGraph re-scored
  5. 2026-11-13 13:50 UTCGHSA enrichmentGHSA-pcrw-h46h-c93h · GitHub severity CRITICAL · GitHub CVSS 9.8
  6. 2026-11-12 19:28 UTCEchelonGraph re-scored
  7. 2026-11-12 19:28 UTCGHSA enrichmentGHSA-pcrw-h46h-c93h · GitHub severity CRITICAL · GitHub CVSS 9.8
  8. 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  9. 2026-11-11 20:48 UTCEchelonGraph re-scored
  10. 2026-11-11 20:48 UTCGHSA enrichmentGHSA-pcrw-h46h-c93h · GitHub severity CRITICAL · GitHub CVSS 9.8
  11. 2026-11-11 16:38 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  12. 2026-11-10 19:54 UTCEchelonGraph re-scored
  13. 2026-11-10 19:54 UTCGHSA enrichmentGHSA-pcrw-h46h-c93h · GitHub severity CRITICAL · GitHub CVSS 9.8
  14. 2026-11-10 16:42 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  15. 2026-11-09 23:00 UTCENISA EUVD ID recordedEUVD-2026-120503 · Source: ENISA EUVD
  16. 2026-11-09 22:40 UTCEchelonGraph re-scoredFirst assessed: 9.8 CRITICAL
  17. 2026-11-09 22:39 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-125120?
CVE-2026-125120 is a critical-severity vulnerability; its CVE record was published on November 9, 2026. Mongoose is a MongoDB object modeling tool designed to work in an asynchronous environment. Prior to 6.13.11, 7.8.12, 8.24.3, and 9.9.2, Mongoose countDocuments() does not apply the configured sanitizeFilter query selector injection defense. An application that enables sanitizeFilter and passes…
When was the CVE record for CVE-2026-125120 published?
The CVE record for CVE-2026-125120 was published on November 9, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 13, 2026; the record at its source may have been updated since.
Is CVE-2026-125120 actively exploited?
CVE-2026-125120 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (47th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-125120?
CVE-2026-125120 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-125120?
A fix for CVE-2026-125120 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-125120 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-125120

Explore →

Is Your Infrastructure Affected by CVE-2026-125120?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.