CVE-2026-125117 json
Mongoose walks into inherited properties when hydrating, setting, and merging, allowing overwrites of built-in functions (denial of service) and shared schema state
published 9d ago modified yesterday also EUVD-2026-120498 , GHSA-8332-j7wj-wjw4
- cvss
- 8.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 48%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- npm mongoose 6.13.12, 7.8.13, 8.24.7, 9.11.4
- github.com/Automattic/mongoose@18b5513 commit
- github.com/Automattic/mongoose@2a195d1 commit
- github.com/Automattic/mongoose@3cb702b commit
- github.com/Automattic/mongoose@85cf897 commit
- github.com/Automattic/mongoose@8cee51b commit
- github.com/Automattic/mongoose@8eb74cb commit
- github.com/Automattic/mongoose/releases/tag/6.13.12 release
- github.com/Automattic/mongoose/releases/tag/7.8.13 release
- github.com/Automattic/mongoose/releases/tag/8.24.7 release
- github.com/Automattic/mongoose/releases/tag/9.11.4 release
Is CVE-2026-125117 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-125117 updated cvss 8.2
mongoose: mongoose: Denial of Service via unsafe inherited property traversal
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- partial
- Assessed
- yesterday
Exploit prediction
0.58% chance of exploitation in the next 30 days, higher than 48% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- github.com https://github.com/Automattic/mongoose/security/advisories/GHSA-8332-j7wj-wjw4 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.2 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H |
| GitHub | 3.1 | 8.2 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | mongoose | <6.13.12 >=7.0.0, <7.8.13 >=8.0.0, <8.24.7 >=9.0.0, <9.11.4 |
6.13.12 7.8.13 8.24.7 9.11.4 |
Affected products
- Automattic mongoose
Classification
- Weakness
-
- CWE-1321 Improperly Controlled Modification of Object Prototype Attributes
References
-
github.com
/Automattic/mongoose/commit/18b5513dd463731a2caf0d3395ef1d9eb0735f50
web
-
github.com
/Automattic/mongoose/commit/2a195d19a4dd240f039a0a226614d5804e8187ee
web
-
github.com
/Automattic/mongoose/commit/3cb702b8d079c3e267f0b10f41673a1590f703c8
web
-
github.com
/Automattic/mongoose/commit/85cf897105edfeb5f56be42a18a68704434cac82
web
-
github.com
/Automattic/mongoose/commit/8cee51beead554df1f3d05645edb439c69eb2a9b
web
-
github.com
/Automattic/mongoose/commit/8eb74cb4a550cbe0225963b07aebacbd999d4b74
web
-
github.com
/Automattic/mongoose/security/advisories/GHSA-8332-j7wj-wjw4
exploit, web, advisory
-
github.com
/Automattic/mongoose/releases/tag/6.13.12
web
-
github.com
/Automattic/mongoose/releases/tag/7.8.13
web
-
github.com
/Automattic/mongoose/releases/tag/8.24.7
web
-
github.com
/Automattic/mongoose/releases/tag/9.11.4
web
-
nvd.nist.gov
/vuln/detail/CVE-2026-125117
advisory
-
github.com
/Automattic/mongoose
package
Sources
- CVE List CVE-2026-125117
- GitHub Advisory GHSA-8332-j7wj-wjw4
- NVD CVE-2026-125117
- Maintainer advisory GHSA-8332-j7wj-wjw4
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of Automattic/mongoose published their own advisory on GitHub. Reviewed sources take precedence over it.