Skip to content
Web

CVE-2026-73649

CRITICAL
Critical
EPSS 0.50%Patch availableAug 14, 2026

Template injection in Velocity.js enables server-side remote code execution.

common questions

Is CVE-2026-73649 being exploited?

Not confirmed. CVE-2026-73649 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.50% probability of exploitation in the next 30 days.

How severe is CVE-2026-73649?

CVE-2026-73649 is rated Critical. 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-73649?

Yes. A fix has been recorded for CVE-2026-73649. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-73649 affect?

CVE-2026-73649 affects Velocity.js < 2.1.7, Node.js apps using Velocity.js, Server processes rendering untrusted templates. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-73649?

Upgrade to Velocity.js 2.1.7 and audit/sanitize templates; restrict template input.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Velocity.js < 2.1.7Node.js apps using Velocity.jsServer processes rendering untrusted templates
impact

Remote code execution via attacker-controlled templates; allows shell execution, environment & cloud-credential access, and internal-network access from the server.

action required

Immediate action required

affected versions
shepherdwind velocity.js
  • affected< 2.1.7

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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free