Mongoose: sanitizeFilter not applied on countDocuments

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2026-125120: 0.57% estimated exploitation activity in the next 30 days; percentile 47.31 (FIRST EPSS, 2026-11-10). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact `sanitizeFilter` is Mongoose's mechanism for protecting against query selector injection attacks. In older versions of Mongoose, `sanitizeFilter` was not applied for `countDocuments()` queries.

Patches Patches have been released for all supported Mongoose major release lines. Please upgrade to the following versions depending on which major version of Mongoose applications are using. 1. `^9.9.2` 2. `^8.24.3` 3. `^7.8.12` 4. `^6.13.11`

Workarounds Middleware: ```javascript mongoose.plugin(function() { schema.pre('countDocuments', function() { // This will always apply `sanitizeFilter` on `countDocuments` mongoose.sanitizeFilter(this.getFilter()); }); }); ```

Published by the source

10 Nov 2026, 19:37 UTC

Last modified by the source

10 Nov 2026, 19:45 UTC

Source last checked

11 Nov 2026, 06:00 UTC

1. Revision 2 · amended · 11 Nov 2026

   Amended from osv record GHSA-pcrw-h46h-c93h

2. Revision 1 · created · 10 Nov 2026

   Published from ghsa record GHSA-pcrw-h46h-c93h

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-125120

Advisory: Mongoose: sanitizeFilter not applied on countDocuments
IDs: CVE-2026-125120, GHSA-pcrw-h46h-c93h
Record: https://patchnext.com/advisories/cve-2026-125120 (revision 2, source checked 11 Nov 2026, 06:00 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: mongoose 9.9.2, 8.24.3, 7.8.12, 6.13.11. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm mongoose: affected < 6.13.11; >= 7.0.0, < 7.8.12; >= 8.0.0, < 8.24.3; >= 9.0.0, < 9.9.2; fixed in 9.9.2, 7.8.12, 8.24.3, 6.13.11

## Suggested inspection (read-only)
- `npm ls mongoose --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on mongoose.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-pcrw-h46h-c93h (GitHub-reviewed advisory GHSA-pcrw-h46h-c93h lists affected ranges: npm mongoose >=0 =7.0.0 =8.0.0 =9.0.0 <9.9.2)
- Verified: https://osv.dev/vulnerability/GHSA-pcrw-h46h-c93h (OSV record GHSA-pcrw-h46h-c93h lists affected ranges: npm mongoose >=0 =7.0.0 =8.0.0 =9.0.0 <9.9.2 (fixed))

Commands are suggestions: review each one before running it.