CVE-2026-34221: MikroORM has Prototype Pollution in Utils.merge
A prototype pollution vulnerability exists in the Utils.merge helper used internally by MikroORM when merging object structures. The function did not prevent special keys such as proto, constructor, or prototype, allowing attacker-controlled input to modify the JavaScript object prototype when merged.
Published Mar 29, 2026 · Updated Mar 31, 2026
Affected packages
@mikro-orm/core
- Ecosystem
- npm
- Affected
- < 6.6.10
- Fixed in
- 6.6.10
- Check
npm ls @mikro-orm/core
@mikro-orm/core
- Ecosystem
- npm
- Affected
- >= 7.0.0-dev.0, < 7.0.6
- Fixed in
- 7.0.6
- Check
npm ls @mikro-orm/core
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
A prototype pollution vulnerability exists in the Utils.merge helper used internally by MikroORM when merging object structures.
The function did not prevent special keys such as __proto__, constructor, or prototype, allowing attacker-controlled input to modify the JavaScript object prototype when merged.
Exploitation requires application code to pass untrusted user input into ORM operations that merge object structures, such as entity property assignment or query condition construction.
Prototype pollution may lead to denial of service or unexpected application behavior. In certain scenarios, polluted properties may influence query construction and potentially result in SQL injection depending on application code.
Credited to lukas-eu.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
