SQL Injection in @mikro-orm/sql (CVE-2026-44680)
Summary
SQL injection in @mikro-orm/sql (CVE-2026-44680). Confidential information can be exposed externally. Exploitable via Platform.quoteIdentifier. Mitigation: upgrade to 7.0.14 or later.
Original description
The description as published by the source.
MikroORM is a TypeScript ORM for Node.js based on Data Mapper, Unit of Work and Identity Map patterns. Prior to @mikro-orm/knex 6.6.14 and @mikro-orm/sql 7.0.14, MikroORM's identifier-quoting helper (Platform.quoteIdentifier and the postgres/mssql overrides) and its JSON-path emitters (Platform.getSearchJsonPropertyKey, quoteJsonKey) did not properly escape characters that delimit the SQL identifier or string-literal context they emit into. When application code passes attacker-influenced strings to public ORM APIs that expect an identifier or a JSON-property filter, an attacker can break out of the quoted context and inject arbitrary SQL. This vulnerability is fixed in @mikro-orm/knex 6.6.14 and @mikro-orm/sql 7.0.14.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-44680 has been found in @mikro-orm/sql.
Attackers can target a specific entry point like Platform.quoteIdentifier over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.6/10.
What to do: upgrade @mikro-orm/sql to 7.0.14 or later.
If unsure, ask your IT team or search "@mikro-orm/sql CVE-2026-44680" on the vendor's site.
CVE-2026-44680 (@mikro-orm/sql) — CWE-89 / CVSS v3 7.6
Attack vector: remote (network-reachable) / no user interaction
Attack surface: Platform.quoteIdentifier / Platform.getSearchJsonPropertyKey / quoteJsonKey / schema
Patched: 7.0.14 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
SQL injection (CWE-89) exists in @mikro-orm/sql. Attackers reach the vulnerable code path via Platform.quoteIdentifier.
Check the vendor advisory for the affected versions of @mikro-orm/sql. Attack surface: Platform.quoteIdentifier / Platform.getSearchJsonPropertyKey / quoteJsonKey / schema.
Severity: High (CVSS 7.6/10). Confidential information can be exposed externally.
Update to 7.0.14.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@mikro-orm/sql' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@mikro-orm/sql' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@mikro-orm/sqlを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @mikro-orm/sql to 7.0.14ステージング環境で 7.0.14 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- patch github.com
- patch github.com
- patch github.com
- web github.com