Quick answers
- Is CVE-2026-125116 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-125116 being exploited in the wild.
- How severe is CVE-2026-125116?
- Medium severity, with a CVSS score of 4.8, published 9 November 2026.
- Which products and versions are affected?
- Mongoose <unknown; mongoose (npm) < 6.13.12, SEMVER:introduced=0,fixed=6.13.12.
- Is there a fix for CVE-2026-125116?
- Yes. mongoose (npm): upgrade to 6.13.12 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-125116 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-125116?
- Check whether you run Mongoose or mongoose (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- mongoose (npm): upgrade to 6.13.12 or later
npm install mongoose@6.13.12
Technical details
Mongoose's discriminator lookup uses plain object property access on registries without checking for inherited properties, allowing values like 'constructor' or 'toString' to resolve to Object.prototype methods. When combined with `bulkWrite(..., { skipValidation: true })`, raw unvalidated documents can be persisted directly to MongoDB. Query results containing such documents may throw errors during hydration, causing denial of service across all users until the document is manually removed.
Affected products
- Mongoose Mongoose <unknown
Identifiers
- CVE-2026-125116
- GHSA-wr5m-5jph-8m96
Timeline
- 2026-11-10: disclosed