Code Injection in typeorm (CVE-2026-73651)
Summary
Code injection in typeorm (CVE-2026-73651). Confidential information can be exposed externally. Exploitable via MigrationGenerateCommand.ts. Mitigation: upgrade to 1.1.0 or later.
Original description
The description as published by the source.
TypeORM is a TypeScript and JavaScript ORM for Node.js that supports PostgreSQL, MySQL, MariaDB, SQLite, SQL Server, Oracle, and other databases. Prior to versions 0.3.31 and 1.1.0, typeorm migration:generate embeds database schema metadata into JavaScript or TypeScript template literals in src/commands/MigrationGenerateCommand.ts, escaping backticks but not ${...} interpolation. An attacker with database schema write access can place a payload in column COMMENT or DEFAULT metadata, or another introspected schema string, and the JavaScript engine evaluates the payload when the generated migration is loaded through migration:run, import, or require. This issue is fixed in versions 0.3.31 and 1.1.0.
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-73651 has been found in typeorm.
Attackers can target a specific entry point like MigrationGenerateCommand.ts over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 5.7/10.
What to do: upgrade typeorm to 1.1.0 or later.
If unsure, ask your IT team or search "typeorm CVE-2026-73651" on the vendor's site.
CVE-2026-73651 (typeorm) — CWE-94 / CVSS v3 5.7
Attack vector: remote (network-reachable)
Attack surface: MigrationGenerateCommand.ts / DEFAULT / COMMENT / CHECK
Patched: 1.1.0 — 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.
Arbitrary code execution (CWE-94) exists in typeorm. Attackers reach the vulnerable code path via MigrationGenerateCommand.ts.
Check the vendor advisory for the affected versions of typeorm. Attack surface: MigrationGenerateCommand.ts / DEFAULT / COMMENT / CHECK.
Severity: Medium (CVSS 5.7/10). Confidential information can be exposed externally.
Update to 1.1.0.
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 'typeorm' . 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 'typeorm' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
typeormを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade typeorm to 1.1.0ステージング環境で 1.1.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- patch github.com
- patch github.com
- web github.com
- web github.com
- web github.com