@mikro-orm/core
Affected
- introduced
0, fixed6.6.10(semver)
Fixed versions
6.6.10
Fix
- Fixed version
6.6.10npm install @mikro-orm/[email protected]
Advisory
Also known as: CVE-2026-34220
MikroORM is vulnerable to SQL Injection via specially crafted object
Summary
MikroORM versions <= 6.6.9 and <= 7.0.5 are vulnerable to SQL injection when specially crafted objects are interpreted as raw SQL query fragments.
Impact
If user-controlled input is passed directly to MikroORM query construction APIs, an attacker may inject raw SQL fragments. This can lead to SQL injection depending on the database and query being executed.
Affected usage
The issue occurs when untrusted objects are passed to ORM write APIs such as:
wrap(entity).assign(userInput) followed by em.flush()em.nativeUpdate()em.nativeInsert()em.create() followed by em.flush()Applications that validate input types or enforce strict schema validation before passing data to MikroORM are not affected.
Fix
The vulnerability was caused by duck-typed detection of internal ORM marker properties.
The fix replaces these checks with symbol-based markers that cannot be reproduced by user input.
Critical Basis: The source's own band: CRITICAL
0, fixed 6.6.10 (semver)6.6.10
6.6.10npm install @mikro-orm/[email protected]7.0.0-dev.0, fixed 7.0.6 (semver)7.0.6
7.0.6npm install @mikro-orm/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0