{"answers":{"affected":"2 open source packages ship an affected version, including velocityjs.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-73649 exists.","fix":"Upgrade velocityjs to 2.1.7 or later.","what":"CVE-2026-73649 is a critical code injection vulnerability in shepherdwind velocity.js, published on 13 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-73649 and fix it if it is affected.\n\nWhat it is: CVE-2026-73649 is a critical code injection vulnerability in shepherdwind velocity.js, published on 13 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-73649 exists.\n\nAffected packages and fixed versions:\n- velocityjs (npm): affected all versions; fixed in 2.1.7\n- velocityjs (npm): affected all versions; fixed in 2.1.7\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-73649/ (Markdown: https://insights.sbomify.com/CVE-2026-73649/index.md)","id":"CVE-2026-73649","markdown":"https://insights.sbomify.com/CVE-2026-73649/index.md","name":"CVE-2026-73649","record":{"aliases":["GHSA-7gfh-x38p-prh3","ROOT-APP-NPM-GHSA-7gfh-x38p-prh3"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript template engine","requires_auth":"none","summary":"Attackers can execute arbitrary code by exploiting unfiltered property reads in Velocity.js templates, bypassing previous security fixes.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"Velocity.js is a JavaScript implementation of the Apache Velocity template engine. Prior to 2.1.7, the earlier fix for CVE-2026-44966 filtered constructor, __proto__, and prototype only in the #set assignment handler in src/compile/set.ts, while property-read expressions in src/compile/references.ts remained unfiltered. The getReferences() flow called getAttributes(), whose property access allowed an attacker-controlled template to traverse constructor.constructor to the JavaScript Function constructor. The #set handler validated only the assignment target and did not inspect the right-hand property-read expression, allowing arbitrary shell commands, environment-variable access, cloud-credential access, and internal-network access in the server process. This issue is fixed in version 2.1.7.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Velocity.js: Remote Code Execution via property-read to Function constructor (bypass of CVE-2026-44966 fix)","id":"CVE-2026-73649","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"SVGO: removeScripts plugin leaves some executable scripts intact","id":"CVE-2026-73650"},"packages":[{"ecosystem":"npm","fixed":["2.1.7"],"introduced":["0"],"last_affected":[],"package":"velocityjs","purl":null,"source":"GHSA-7gfh-x38p-prh3"},{"ecosystem":"npm","fixed":["2.1.7"],"introduced":["0"],"last_affected":[],"package":"velocityjs","purl":"pkg:npm/velocityjs","source":"GHSA-7gfh-x38p-prh3"}],"prev":{"headline":"rails-html-sanitizer: Possible XSS vulnerability with certain configurations","id":"CVE-2026-73648"},"products":["velocity.js"],"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":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-08-14","vendors":["shepherdwind"]},"summary":"Attackers can execute arbitrary code by exploiting unfiltered property reads in Velocity.js templates, bypassing previous security fixes.","url":"https://insights.sbomify.com/CVE-2026-73649/"}