{"answers":{"affected":"4 open source packages ship an affected version, including typeorm.","exploited":"There is no known exploitation of CVE-2026-73651 in the wild and no public exploit code.","fix":"Upgrade typeorm to a fixed version for your release line: 0.3.31 or 1.1.0.","what":"CVE-2026-73651 is a medium-severity code injection vulnerability in typeorm, published on 13 Aug 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-73651 and fix it if it is affected.\n\nWhat it is: CVE-2026-73651 is a medium-severity code injection vulnerability in typeorm, published on 13 Aug 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-73651 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- typeorm (npm): affected all versions; fixed in 0.3.31\n- typeorm (npm): affected all versions; fixed in 0.3.31\n- typeorm (npm): affected from 1.0.0; fixed in 1.1.0\n- typeorm (npm): affected from 1.0.0; fixed in 1.1.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-73651/ (Markdown: https://insights.sbomify.com/CVE-2026-73651/index.md)","id":"CVE-2026-73651","markdown":"https://insights.sbomify.com/CVE-2026-73651/index.md","name":"CVE-2026-73651","record":{"aliases":["GHSA-2rp8-mm9q-fp49","MINI-xm3q-cpv7-3r5g","ROOT-APP-NPM-GHSA-2rp8-mm9q-fp49"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"TypeORM Node.js ORM","requires_auth":"high_privilege","summary":"Attackers with database schema write access can inject code via metadata, leading to execution when migrations are generated and loaded.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.7,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"TypeORM: migration:generate template-literal code injection","id":"CVE-2026-73651","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":4,"n_references":5,"next":{"headline":"vantage6: Algorithm developer can edit another developer's algorithm that is pending / under review","id":"CVE-2026-73652"},"packages":[{"ecosystem":"npm","fixed":["0.3.31"],"introduced":["0"],"last_affected":[],"package":"typeorm","purl":null,"source":"GHSA-2rp8-mm9q-fp49"},{"ecosystem":"npm","fixed":["0.3.31"],"introduced":["0"],"last_affected":[],"package":"typeorm","purl":"pkg:npm/typeorm","source":"GHSA-2rp8-mm9q-fp49"},{"ecosystem":"npm","fixed":["1.1.0"],"introduced":["1.0.0"],"last_affected":[],"package":"typeorm","purl":null,"source":"GHSA-2rp8-mm9q-fp49"},{"ecosystem":"npm","fixed":["1.1.0"],"introduced":["1.0.0"],"last_affected":[],"package":"typeorm","purl":"pkg:npm/typeorm","source":"GHSA-2rp8-mm9q-fp49"}],"prev":{"headline":"SVGO: removeScripts plugin leaves some executable scripts intact","id":"CVE-2026-73650"},"products":["typeorm"],"published":"2026-08-13","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-08-14","vendors":["typeorm"]},"summary":"Attackers with database schema write access can inject code via metadata, leading to execution when migrations are generated and loaded.","url":"https://insights.sbomify.com/CVE-2026-73651/"}