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.
CVE-2026-73651
This medium-severity CVE scores 5.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 86% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.7
- EG Score
- 5.7(medium)
- EG Risk
- 26(Track)EG Risk 26/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity57% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 14%
- KEV
- Not listed
Published
August 13, 2026
Last Modified
August 14, 2026
Advisory Details (5)
Auto-updated Aug 13, 20261.1.0
Patch available: typeorm/typeorm 1.1.0
https://github.com/typeorm/typeorm/releases/tag/1.1.00.3.31
Patch available: typeorm/typeorm 0.3.31
https://github.com/typeorm/typeorm/releases/tag/0.3.31commit b175f9b8be42 (typeorm/typeorm)
Patch available: typeorm/typeorm 0.3.31 (contains commit b175f9b8be42)
https://github.com/typeorm/typeorm/commit/b175f9b8be422edd2a2ac035ba90c3f2ce782dfecommit 41d1c62fe49f (typeorm/typeorm)
Patch available: typeorm/typeorm 1.1.0 (contains commit 41d1c62fe49f)
https://github.com/typeorm/typeorm/commit/41d1c62fe49f99c3ca916d4d986f61ee9f45d519migration:generate template-literal code injection · Advisory · typeorm/typeorm · GitHub
https://github.com/typeorm/typeorm/security/advisories/GHSA-2rp8-mm9q-fp49Vendor Advisories for CVE-2026-73651(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| typeorm | — | 0.3.31 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 26× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 09:16 UTCEG score recompute
- 2026-08-24 10:14 UTCEG score recompute
- 2026-08-23 11:11 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 12:09 UTCEG score recompute
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 13:06 UTCEG score recompute
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 14:03 UTCEG score recompute
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 15:46 UTCEG score recompute
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-17 16:43 UTCEG score recompute
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 17:41 UTCEG score recompute
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 02:15 UTCEPSS rescore
- 2026-08-15 18:39 UTCEG score recompute
- 2026-08-15 01:31 UTCEPSS rescore
- 2026-08-14 19:36 UTCEG score recompute
- 2026-08-13 19:19 UTCEG score recompute
- 2026-08-13 18:32 UTCEG score recompute
Show 1 moreShow fewer
- 2026-08-13 18:31 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-94
- CVE-2003-1432EG 10.0EPSS p94HIGH
- CVE-2002-0495EG 10.0EPSS p96HIGH
- CVE-1999-0702EG 10.0EPSS p98HIGH
- CVE-1999-0509EG 10.0EPSS p98HIGH
- CVE-2006-1318EG 9.3EPSS p97HIGH
- CVE-2006-1301EG 9.3EPSS p95HIGH
- CVE-2006-1308EG 9.3EPSS p95HIGH
- CVE-2006-1309EG 9.3EPSS p95HIGH
- CVE-2006-1304EG 9.3EPSS p96HIGH
- CVE-2006-1306EG 9.3EPSS p95HIGH
Frequently asked(5)
What is CVE-2026-73651?
When was CVE-2026-73651 disclosed?
Is CVE-2026-73651 actively exploited?
What is the CVSS score of CVE-2026-73651?
How do I remediate CVE-2026-73651?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-73651
Is Your Infrastructure Affected by CVE-2026-73651?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.