Mongoose: Connection-level sanitizeFilter not applied

Exploitation

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

CVSS

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

EPSS

• CVE-2026-125119: 0.54% estimated exploitation activity in the next 30 days; percentile 45.82 (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.

Summary sanitizeFilter exists to stop query selector injection: it wraps operator objects such as `{ $ne: null }` in filter values in `$eq`, so they are matched literally. Set on a connection with `mongoose.connect()` or `createConnection(uri, { sanitizeFilter: true })`, the connection reports it as enabled but queries never apply it. An application that relies on the connection-level option and passes an attacker-controlled object into a filter therefore remains open to selector injection, and a password value of `{ $ne: null }` returns the account record without the password.

Details `NativeConnection#createClient()` at `lib/drivers/node-mongodb-native/connection.js:270-272` moves `options.sanitizeFilter` into `Connection.config` and deletes the original option. `Query#_castConditions()` at `lib/query.js:2413-2423` checks `Connection.options`, the global `options`, and the per-query options, but never `Connection.config`. The defense therefore does not run even though…

Published by the source

10 Nov 2026, 19:56 UTC

Last modified by the source

10 Nov 2026, 20:00 UTC

Source last checked

11 Nov 2026, 06:00 UTC

1. Revision 2 · amended · 11 Nov 2026

   Amended from osv record GHSA-gg4r-jv3p-qx3c

2. Revision 1 · created · 10 Nov 2026

   Published from ghsa record GHSA-gg4r-jv3p-qx3c

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

# Patch Next advisory brief: CVE-2026-125119

Advisory: Mongoose: Connection-level sanitizeFilter not applied
IDs: CVE-2026-125119, GHSA-gg4r-jv3p-qx3c
Record: https://patchnext.com/advisories/cve-2026-125119 (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: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: mongoose 9.11.4, 8.24.7, 7.8.13, 6.13.12. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm mongoose: affected >= 6.0.0, < 6.13.12; >= 7.0.0, < 7.8.13; >= 8.0.0, < 8.24.7; >= 9.0.0, < 9.11.4; fixed in 6.13.12, 7.8.13, 8.24.7, 9.11.4

## 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-gg4r-jv3p-qx3c (GitHub-reviewed advisory GHSA-gg4r-jv3p-qx3c lists affected ranges: npm mongoose >=6.0.0 =7.0.0 =8.0.0 =9.0.0 <9.11.4)
- Verified: https://osv.dev/vulnerability/GHSA-gg4r-jv3p-qx3c (OSV record GHSA-gg4r-jv3p-qx3c lists affected ranges: npm mongoose >=6.0.0 =7.0.0 =8.0.0 =9.0.0 <9.11.4 (fixed))

Commands are suggestions: review each one before running it.