CVE-2026-125116: Mongoose: Discriminator key values matching inherited properties (e.g. __t: 'constructor') bypass schema casting and can poison collections
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 uses attacker-controlled discriminator key values, including the default t field, to index plain-object registries such as Model.discriminators and schema.discriminators without requiring an own property. Values such as constructor, toString, or hasOwnProperty can therefore resolve to inherited built-in functions instead of a registered discriminator, causing type confusion in model construction, document creation, hydration, query and update casting, embedded discriminators, and populate operations. In the bulkWrite() insertOne path with skipValidation enabled, a constructor value can cause a raw input object to be stored without schema casting or strict filtering, and a stored poisoned document can make every query that hydrates it fail until the document is removed. The weakness reads inherited properties but does not modify Object.prototype and is not prototype pollution. 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 applications are exposed in default configurations?
Applications using affected Mongoose versions are exposed when untrusted input can control a discriminator key value. The default discriminator key, __t, is included, so a custom discriminator-key configuration is not required.
What input is required to trigger the issue?
An attacker must supply a discriminator value matching an inherited object property, such as constructor, toString, or hasOwnProperty. These values can resolve to built-in inherited functions rather than registered discriminators.
When can this lead to uncast data being stored?
The described raw-storage path requires bulkWrite() with an insertOne operation and skipValidation enabled. A constructor discriminator value can then cause the raw input object to be stored without schema casting or strict filtering.
How might an existing poisoned document affect the application?
A stored poisoned document can cause every query that attempts to hydrate it to fail. The described recovery is to remove the poisoned document.
What versions contain the fix?
Upgrade to Mongoose 6.13.12, 7.8.13, 8.24.7, or 9.11.4, depending on the major version in use.