CVE-2026-44966
Prototype pollution in Velocity.js <=2.1.5 via #set; may enable DoS or RCE.
Is CVE-2026-44966 being exploited?
Not confirmed. CVE-2026-44966 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.55% probability of exploitation in the next 30 days.
How severe is CVE-2026-44966?
CVE-2026-44966 is rated High with a CVSS score of 8.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-44966?
Yes. A fix has been recorded for CVE-2026-44966. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-44966 affect?
CVE-2026-44966 affects Velocity.js <= 2.1.5. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-44966?
Upgrade Velocity.js to a fixed version
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attacker-controlled templates can modify Object.prototype, potentially causing DoS or RCE depending on server context.
Patch when possible
- affected<= 2.1.5
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.