Skip to content
Sign in
CVE-2026-1251197.5High

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

Automattic · mongoose

No fix listed · Affected: Automattic mongoose · Exploitation: not established

ExploitationNot established

Not in CISA KEV as of catalogue 2026.11.09 (9 Nov)

  1. In CISA KEV: not seen
  2. Exploited (reported): not seen
  3. Scanning observed: not seen
  4. Proof of concept public: not seen
  5. Not establishedNothing in the sources we check
0.5%probability of exploitation in the next 30 days
45th percentile
050100

Higher than 45% of scored CVEs

7.5HighCVSS
LowHigh

DescriptionNVD

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.

Coverage1 article · 1 outlet

First in our coverage: SecurityOnline, 10 Nov.

  1. Mongoose patches five flaws enabling injection and prototype pollution
    SecurityOnline · first in our coverage · mentions it in passing

New articles also arrive in the RSS feed.

References

Updated AboutDevelopersSign in