| Title | Node.js mingo 7.2.1 Prototype Pollution |
|---|
| Description | mingo version 7.2.1 is affected by a prototype pollution vulnerability in the public mingo/updater export. The package exposes update APIs such as update, updateOne, and updateMany, which apply update operators including $set. When a $set selector contains a path such as __proto__.polluted, the update path traversal follows the __proto__ segment and reaches Object.prototype without filtering dangerous keys.
A minimal reproduction is possible by calling update({}, { $set: { '__proto__.polluted': 'yes' } }), after which newly created objects inherit the polluted property. Applications that pass user-controlled update documents or update paths to mingo/updater may be vulnerable to logic bypass, unexpected property injection, denial of service, or other secondary impact. |
|---|
| Source | ⚠️ https://github.com/kofrasa/mingo/issues/606 |
|---|
| User | wjm1 (UID 98929) |
|---|
| Submission | 06/11/2026 13:52 (1 month ago) |
|---|
| Moderation | 07/14/2026 07:08 (1 month later) |
|---|
| Status | Accepted |
|---|
| VulDB entry | 378245 [kofrasa mingo up to 7.2.1 Update API update/updateOne/updateMany Set prototype pollution] |
|---|
| Points | 20 |
|---|