Bug 2569963 (CVE-2026-125119) - CVE-2026-125119 mongoose: Mongoose: Security feature bypass via ignored connection-level sanitizeFilter option
Summary: CVE-2026-125119 mongoose: Mongoose: Security feature bypass via ignored conne...
Keywords:
Status: NEW
Alias: CVE-2026-125119
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2571531 2571532 2571533
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-11-10 19:27 UTC by OSIDB Bzimport
Modified: 2026-11-11 08:11 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-11-10 19:27:30 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.