Mongoose is a MongoDB object modeling tool designed to work in an asynchronous environment. Prior to 6.13.10, 7.8.10, 8.24.1, and 9.7.2, passing a user-controlled update such as MyModel.updateOne(filter, req.body) can exploit Mongoose update casting with a __proto__.x dotted path under $set. Schema.prototype.path and Schema.prototype._getPathType can treat inherited properties of schema.paths and schema.nested as schema types, allowing the casting process to set $fullPath and $parentSchemaDocArray on Object.prototype before throwing. This prototype pollution makes those properties visible on newly created objects and can cause application integrity and availability impacts. This issue is fixed in versions 6.13.10, 7.8.10, 8.24.1, and 9.7.2.
CVE-2026-73562
This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 70% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.5
- EG Score
- 6.5(medium)
- EG Risk
- 44(Track)EG Risk 44/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity65% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 30%
- KEV
- Not listed
Published
August 13, 2026
Last Modified
August 14, 2026
Advisory Details (5)
Auto-updated Aug 13, 2026commit fab793b74713 (Automattic/mongoose)
Fix landed in Automattic/mongoose commit fab793b74713 — awaiting tagged release
https://github.com/Automattic/mongoose/commit/fab793b747131c68927888cba41cf3e6d6593740commit 953d085bee5a (Automattic/mongoose)
Patch available: Automattic/mongoose 8.24.1 (contains commit 953d085bee5a)
https://github.com/Automattic/mongoose/commit/953d085bee5a16b5d6c5af33a156e6314d6d9a45commit 7285466b860d (Automattic/mongoose)
Patch available: Automattic/mongoose 7.8.10 (contains commit 7285466b860d)
https://github.com/Automattic/mongoose/commit/7285466b860d3b511f8d07b2ab72656703ee707acommit 35a3f33bc9a0 (Automattic/mongoose)
Patch available: Automattic/mongoose 9.7.2 (contains commit 35a3f33bc9a0)
https://github.com/Automattic/mongoose/commit/35a3f33bc9a0a28671f99e3c5010000425650d0fPrototype pollution in mongoose update casting via __proto__-prefixed dotted path (Schema._getSchema/path getter) · Advisory · Automattic/mongoose · GitHub
https://github.com/Automattic/mongoose/security/advisories/GHSA-664h-wqgq-64gwVendor Advisories for CVE-2026-73562(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| mongoose | — | 6.13.10 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 27× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-25 17:12 UTCEG score recompute
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 19:14 UTCEG score recompute
- 2026-08-23 21:27 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 01:54 UTCEG score recompute
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 04:06 UTCEG score recompute
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 06:20 UTCEG score recompute
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 08:33 UTCEG score recompute
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 10:45 UTCEG score recompute
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 15:11 UTCEG score recompute
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 02:15 UTCEPSS rescore
- 2026-08-15 17:24 UTCEG score recompute
- 2026-08-15 01:31 UTCEPSS rescore
- 2026-08-14 19:36 UTCEG score recompute
- 2026-08-14 18:34 UTCEG score recompute
- 2026-08-13 18:18 UTCEG score recompute
Show 2 moreShow fewer
- 2026-08-13 17:47 UTCEG score recompute
- 2026-08-13 17:46 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-1321
- CVE-2020-12079EG 10.0CRITICAL
- CVE-2011-10019EG 9.8EPSS p90CRITICAL
- CVE-2020-28462NVD 7.3EG 9.8CRITICAL
- CVE-2020-28276EG 9.8CRITICAL
- CVE-2020-28271EG 9.8CRITICAL
- CVE-2020-28270EG 9.8CRITICAL
- CVE-2020-28269EG 9.8EPSS p90CRITICAL
- CVE-2020-8158EG 9.8CRITICAL
- CVE-2019-0230EG 9.8EPSS p100CRITICAL
- CVE-2020-7727EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-73562?
When was CVE-2026-73562 disclosed?
Is CVE-2026-73562 actively exploited?
What is the CVSS score of CVE-2026-73562?
How do I remediate CVE-2026-73562?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-73562
Is Your Infrastructure Affected by CVE-2026-73562?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.