CVE-2026-34220

MikroORM is vulnerable to SQL Injection via specially crafted object

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.

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.

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.

Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access. Typical impact: data disclosure or modification.

Kodem intelligence

Already deployed Kodem?

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.

1. What is CVE-2026-34220? CVE-2026-34220 is a critical-severity SQL injection vulnerability in @mikro-orm/core (npm), affecting versions < 6.6.10. It is fixed in 6.6.10, 7.0.6. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.
2. Which versions of @mikro-orm/core are affected by CVE-2026-34220? @mikro-orm/core (npm) versions < 6.6.10 is affected.
3. Is there a fix for CVE-2026-34220? Yes. CVE-2026-34220 is fixed in 6.6.10, 7.0.6. Upgrade to this version or later.
4. Is CVE-2026-34220 exploitable, and should I be worried? Whether CVE-2026-34220 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
5. What actually determines whether CVE-2026-34220 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
6. How do I fix CVE-2026-34220?
   • Upgrade @mikro-orm/core to 6.6.10 or later
   • Upgrade @mikro-orm/core to 7.0.6 or later

Other vulnerabilities in @mikro-orm/core