Mongoose: Prototype pollution via Schema.prototype.virtual()
- Exploited
- No known exploitation
- Fix
- Fixed in 6.13.12, 7.8.13, 8.24.7, 9.11.4
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 6.13.12, 7.8.13, 8.24.7, 9.11.4.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 24/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Mongoose, a MongoDB object modeling tool for Node.js, has a prototype pollution flaw in how it builds nested virtual field paths, which can be reached remotely, without logging in, by anyone who can influence virtual field names in dynamic schemas. An attacker can write properties to core JavaScript prototypes, which can spoof inherited checks such as authorization flags and affect other server-side code.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
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, Schema.prototype.virtual() builds nested virtual paths without applying the special-property validation already used by Schema.path() and Schema.add(). An attacker who can influence virtual field names in dynamic schemas, content-management form builders, or schema-as-code systems can supply path segments such as __proto__, constructor, or prototype, causing the virtual-path reducer to write enumerable properties to Object.prototype or Function.prototype. The resulting prototype pollution can spoof inherited property checks such as authorization flags and can provide function-prototype gadget state to other server-side JavaScript code. This issue is fixed in versions 6.13.12, 7.8.13, 8.24.7, and 9.11.4.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.5/10CVSS 6.5
- No patch0/5No signal
What would change the score
- Would score about 69 if added to CISA KEV
- Would score about 64 if CISA's SSVC rates exploitation active
- Would score about 29 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 6.13.12, 7.8.13, 8.24.7, 9.11.4.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Automattic mongoose
fixed in 6.13.12; From 7.0.0 · fixed in 7.8.13; From 8.0.0 · fixed in 8.24.7; From 9.0.0 · fixed in 9.11.4
Evidence 9
- Advisory
- Repository
- Repository
- Repository
- Repository
Show all 9 sourcesShow fewer sources
- Repository
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-125118
Is CVE-2026-125118 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-125118?
mongoose: before 6.13.12; from 7.0.0 before 7.8.13; from 8.0.0 before 8.24.7; from 9.0.0 before 9.11.4.Source: cve.now feed data
How do I fix CVE-2026-125118?
Upgrade to a fixed version: 6.13.12, 7.8.13, 8.24.7, 9.11.4.Source: cve.now feed data