CVE-2026-125117: Mongoose walks into inherited properties when hydrating, setting, and merging, allowing overwrites of built-in functions (denial of service) and shared schema state
Mongoose is a MongoDB object modeling tool designed to work in an asynchronous environment. Prior to 6.13.12, 7.8.13, 8.24.7, and 9.11.4, Mongoose can descend into inherited properties while loading database documents in init(), setting dotted paths in $set, and merging update documents in utils.mergeClone. Attacker-controlled keys such as toString or valueOf can therefore cause Mongoose to write into shared built-in functions instead of an own property. A crafted document, Mixed path, non-strict document or subdocument, findOneAndReplace() replacement, chained update, or Query.prototype.merge() source can overwrite Object.prototype.toString.call, causing later queries on unrelated models to fail until the process restarts. Separately, when an attacker controls the dotted path passed to doc.set(path, value) for a subdocument configured with strict: false, descent through $set can reach $schema and alter shared validators or schema options for later documents. Mongoose already blocks proto, constructor, and prototype, so this issue overwrites properties on reachable shared objects rather than adding new properties directly to Object.prototype. This issue is fixed in versions 6.13.12, 7.8.13, 8.24.7, and 9.11.4.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
mongooseto a version that resolves this vulnerability.Fixed in 6.13.12 - Upgrade
Upgrade
mongooseto a version that resolves this vulnerability.Fixed in 7.8.13 - Upgrade
Upgrade
mongooseto a version that resolves this vulnerability.Fixed in 8.24.7 - Upgrade
Upgrade
mongooseto a version that resolves this vulnerability.Fixed in 9.11.4
Event History
Frequently Asked Questions
Which Mongoose releases contain the fixes?
Upgrade to 6.13.12, 7.8.13, 8.24.7, 9.11.4, or a later release in the applicable release line.
What attacker-controlled input can trigger the issue?
Relevant inputs include crafted database documents, Mixed paths, non-strict documents or subdocuments, findOneAndReplace() replacement documents, chained updates, and sources supplied to Query.prototype.merge(). A separately described schema-state impact requires attacker control of a dotted path passed to doc.set(path, value) on a subdocument configured with strict: false.
Does exploitation depend on using __proto__, constructor, or prototype keys?
No. Mongoose already blocks those keys; the issue instead allows keys such as toString or valueOf to overwrite properties on reachable shared objects.
How might an existing compromise appear at runtime?
A crafted input can overwrite Object.prototype.toString.call, causing later queries on unrelated models to fail until the process restarts. In the strict:false subdocument case, later documents may use altered shared validators or schema options.