# CVE-2026-125117 — Automattic mongoose

> As of 2026-11-10, CVE-2026-125117 is a HIGH-severity vulnerability in Automattic mongoose, CVSS v3.1 8.2, EPSS 0.5% (48.2th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-125117 as of 2026-11-10; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

**Last updated:** 2026-11-10

## What is CVE-2026-125117?

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.

The record classifies CVE-2026-125117 under weakness class [CWE-1321](https://intel.threadlinqs.com/cwe/CWE-1321). Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs no user interaction, and has high impact on availability. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 7 days ago.

## Severity and exploitation probability

- **CVSS v3.1 base score:** 8.2 — HIGH (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H`)
- **EPSS (FIRST):** 0.5% probability of exploitation in the next 30 days, higher than 48.2% of all scored CVEs
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 6/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-11-09

## Is CVE-2026-125117 being exploited?

It currently carries a trending score of 42 in the Threadlinqs vulnerability feed.

## Affected products and versions

- [Automattic](https://intel.threadlinqs.com/vendors/automattic): mongoose

Affected software packages:

- `npm:mongoose` — patched in 6.13.12
- `npm:mongoose` — patched in 7.8.13
- `npm:mongoose` — patched in 8.24.7
- `npm:mongoose` — patched in 9.11.4

## How to fix CVE-2026-125117

Fixed versions are recorded for 4 packages: npm:mongoose 6.13.12, npm:mongoose 7.8.13, npm:mongoose 8.24.7, npm:mongoose 9.11.4. No vendor patch reference has been recorded for CVE-2026-125117 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

## Threat activity tracking CVE-2026-125117

No threat campaign in the Threadlinqs corpus currently references CVE-2026-125117, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

## Sources

Enriched from CVE.org, NVD, FIRST EPSS, GitHub Security Advisories. This product uses the NVD API but is not endorsed or certified by the NVD.

**Vendor advisory and patch**

- [github.com](https://github.com/Automattic/mongoose/security/advisories/GHSA-8332-j7wj-wjw4)

**Other references**

- [github.com](https://github.com/Automattic/mongoose/commit/18b5513dd463731a2caf0d3395ef1d9eb0735f50)
- [github.com (2a195d19a4dd240f039a0a226614d5804e8187ee)](https://github.com/Automattic/mongoose/commit/2a195d19a4dd240f039a0a226614d5804e8187ee)
- [github.com (3cb702b8d079c3e267f0b10f41673a1590f703c8)](https://github.com/Automattic/mongoose/commit/3cb702b8d079c3e267f0b10f41673a1590f703c8)
- [github.com (85cf897105edfeb5f56be42a18a68704434cac82)](https://github.com/Automattic/mongoose/commit/85cf897105edfeb5f56be42a18a68704434cac82)
- [github.com (8cee51beead554df1f3d05645edb439c69eb2a9b)](https://github.com/Automattic/mongoose/commit/8cee51beead554df1f3d05645edb439c69eb2a9b)

_Showing 6 of 11 recorded references._

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-125117
No Threadlinqs detection currently covers CVE-2026-125117; it is re-checked on every ingest.
Indicator values unlock with TL Creds (https://threadlinqs.com/tl-creds); MCP access for AI agents needs Purple: https://intel.threadlinqs.com/mcp
