Prototype pollution via unfiltered #set path assignment
Published May 26, 2026 · Updated May 26, 2026
Prototype pollution in Velocity.js 2.1.5 and earlier allows remote attackers to modify Object.prototype through crafted #set directives. The #set path-assignment logic in src/compile/set.ts writes arbitrary keys to base objects without blocking proto, constructor, or prototype traversal. Exploitation requires an application to render attacker-controlled templates; the resulting pollution supports process crashes or code execution only through environment-specific behavior.
Summary
What happened
Prototype pollution in Velocity.js 2.1.5 and earlier allows remote attackers to modify Object.prototype through crafted #set directives. The #set path-assignment logic in src/compile/set.ts writes arbitrary keys to base objects without blocking proto, constructor, or prototype traversal. Exploitation requires an application to render attacker-controlled templates; the resulting pollution supports process crashes or code execution only through environment-specific behavior.
The record
- CVE
- CVE-2026-44966
- Published
- May 26, 2026
- Updated
- May 26, 2026
- Vendor
- shepherdwind
- Product
- Velocity.js
- Classifications
- CWE-1321, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 26, 2026CVE publishedPublication date reported by the CVE source.
- May 26, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=<= 2.1.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA-j658-c2gf-x6pq prototype-pollution proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo