CVE-2026-73562 json
Mongoose: Prototype pollution in the update casting via __proto__-prefixed dotted path (Schema._getSchema/path getter)
published 3mo ago modified 18d ago also BIT-mongoose-2026-73562 , EUVD-2026-58176 , GHSA-664h-wqgq-64gw
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 43%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- npm mongoose 6.13.10, 7.8.10, 8.24.1, 9.7.2
- bitnami mongoose 6.13.10, 7.8.10, 8.24.1, 9.7.2
- mongoosejs mongoose 6.13.10, 7.8.10, 8.24.1, 9.7.2
- github.com/Automattic/mongoose@35a3f33 commit
- github.com/Automattic/mongoose@7285466 commit
- github.com/Automattic/mongoose@953d085 commit
- github.com/Automattic/mongoose@fab793b commit
- github.com/Automattic/mongoose@f494b84 commit
- github.com/Automattic/mongoose#16230 pull request
- github.com/Automattic/mongoose/releases/tag/6.13.10 release
- github.com/Automattic/mongoose/releases/tag/7.8.10 release
- github.com/Automattic/mongoose/releases/tag/8.24.1 release
- github.com/Automattic/mongoose/releases/tag/9.7.2 release
Is CVE-2026-73562 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 FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 2mo ago
Exploit prediction
0.50% chance of exploitation in the next 30 days, higher than 43% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L |
| GitHub | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L |
| OSV | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | mongoose | <6.13.10 >=7.0.0, <7.8.10 >=8.0.0, <8.24.1 >=9.0.0, <9.7.2 |
6.13.10 7.8.10 8.24.1 9.7.2 |
| bitnami | mongoose | <6.13.10 >=7.0.0, <7.8.10 >=8.0.0, <8.24.1 >=9.0.0, <9.7.2 |
6.13.10 7.8.10 8.24.1 9.7.2 |
Affected products
- Automattic mongoose
Classification
- Weakness
-
- CWE-1321 Improperly Controlled Modification of Object Prototype Attributes
References
-
github.com
/Automattic/mongoose/commit/35a3f33bc9a0a28671f99e3c5010000425650d0f
web
-
github.com
/Automattic/mongoose/commit/7285466b860d3b511f8d07b2ab72656703ee707a
web
-
github.com
/Automattic/mongoose/commit/953d085bee5a16b5d6c5af33a156e6314d6d9a45
web
-
github.com
/Automattic/mongoose/commit/fab793b747131c68927888cba41cf3e6d6593740
web
-
github.com
/Automattic/mongoose/pull/16230
web
-
github.com
/Automattic/mongoose/commit/f494b8430f9097fc70446d6949c8a42a27518e0b
web
-
github.com
/Automattic/mongoose/security/advisories/GHSA-664h-wqgq-64gw
web, advisory
-
github.com
/Automattic/mongoose
package
-
github.com
/Automattic/mongoose/releases/tag/6.13.10
web
-
github.com
/Automattic/mongoose/releases/tag/7.8.10
web
-
github.com
/Automattic/mongoose/releases/tag/8.24.1
web
-
github.com
/Automattic/mongoose/releases/tag/9.7.2
web
-
nvd.nist.gov
/vuln/detail/CVE-2026-73562
web
Sources
- CVE List CVE-2026-73562
- GitHub Advisory GHSA-664h-wqgq-64gw
- NVD CVE-2026-73562
- OSV BIT-mongoose-2026-73562
- Maintainer advisory GHSA-664h-wqgq-64gw
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.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.