CVE-2026-34220
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMikroORM is a TypeScript ORM for Node.js based on Data Mapper, Unit of Work and Identity Map patterns. Prior to versions 6.6.10 and 7.0.6, there is a SQL injection vulnerability when specially crafted objects are interpreted as raw SQL query fragments. This issue has been patched in versions 6.6.10 and 7.0.6.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceMikroORM versions prior to 6.6.10 and 7.0.6 contain a SQL injection vulnerability where specially crafted objects are interpreted as raw SQL query fragments, allowing attackers to inject arbitrary SQL commands.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 6.6.10>= 7.0.0, < 7.0.6CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed MikroORM versionRun 'npm list @mikro-orm/core' or check package.json for @mikro-orm/core versionAffected if Version is below 6.6.10, or between 7.0.0 and 7.0.5 (inclusive)
-
Inspect query builder usage for object injection pointsSearch codebase for query builder methods like .where(), .andWhere(), .orWhere() that accept objects from user input (req.body, req.query, route parameters)Affected if Application passes user-supplied objects directly to query builder methods without sanitization
-
Review raw SQL fragment handlingSearch for raw() or similar methods in MikroORM query builder code that could accept maliciously crafted objectsAffected if Code uses raw SQL fragment injection patterns with unsanitized object inputs
You are affected if your MikroORM version is below 6.6.10 or between 7.0.0-7.0.5 AND your application passes user-controlled objects to query builder methods.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped6.6.107.0.6
Upgrade MikroORM to version 6.6.10 or 7.0.6 to apply the patch.
Upgrade to MikroORM 6.6.10 (for 6.x users) or 7.0.6 (for 7.x users)
- Identify the current MikroORM version in your project by checking package.json
- For projects on MikroORM 6.x: Run `npm install [email protected]` or `yarn add [email protected]`
- For projects on MikroORM 7.x: Run `npm install [email protected]` or `yarn add [email protected]`
- After upgrading, run your test suite to verify the application still functions correctly
- Rebuild and redeploy your application
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34220 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-34220 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data