# CVE-2026-73649: Velocity.js: Remote Code Execution via property-read to Function constructor (bypass of CVE-2026-44966 fix)

> Attackers can execute arbitrary code by exploiting unfiltered property reads in Velocity.js templates, bypassing previous security fixes.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Aug 2026
- **Updated:** 14 Aug 2026
- **Also known as:** GHSA-7gfh-x38p-prh3, ROOT-APP-NPM-GHSA-7gfh-x38p-prh3

## What is CVE-2026-73649?

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.

### Official 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.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2026-73649?

2 open source packages ship an affected version, including velocityjs.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `velocityjs` | npm | All versions | 2.1.7 |
| `velocityjs` | npm | All versions | 2.1.7 |

## How do I fix CVE-2026-73649?

Upgrade velocityjs to 2.1.7 or later.

## Is CVE-2026-73649 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-73649 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-73649 and fix it if it is affected.

What 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-73649 exists.

Affected packages and fixed versions:
- velocityjs (npm): affected all versions; fixed in 2.1.7
- velocityjs (npm): affected all versions; fixed in 2.1.7

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-73649/ (Markdown: https://insights.sbomify.com/CVE-2026-73649/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-73649
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-73649
- OSV: https://osv.dev/vulnerability/CVE-2026-73649

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-73649/
Summaries are generated and may contain mistakes; the official description above is the record.