← Back
CVE-2026-73651
medium
CVSS 5.7
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.
AI summary snake-internal / snake-material-v2
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.
❓ What is the problem
**arbitrary code execution** (CWE-94) exists in typeorm. Attackers reach the vulnerable code path via ``MigrationGenerateCommand.ts`` without authentication.
📍 Affected scope
typeorm — . Attack surface: `MigrationGenerateCommand.ts` / `DEFAULT` / `COMMENT` / `CHECK`.
🔥 Severity
Severity: Medium (CVSS 5.7/10). Confidential information can be exposed externally
🔧 How to fix
Update to **1.1.0**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade typeorm to 1.1.0ステージング環境で 1.1.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
typeorm
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.0"}]}]