Skip to main content
VulnerabilityPublished

CVE-2026-73649: shepherdwind velocity.js · Code Injection

Affects shepherdwind velocity.jsSource CVE Database V5

0
Compare

Mentioned vulnerabilities

Not known to be exploited · CVSS 9.8 Critical : upgrade to 2.1.7 as a priority.

Data as of 12 Nov 2026, 23:24 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 54% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.1.7
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

Upgrade velocity.js and shepherdwind/velocity.js to 2.1.7.

Affected software

ProductAffectedFixed in
shepherdwindvelocity.jsAffected
  • <2.1.7
Fixed in
  • 2.1.7
npmshepherdwind/velocity.jspkg:npm/shepherdwind/velocity.jsOther threatsAffected
  • <2.1.7
Fixed in
  • 2.1.7

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade velocity.js to version 2.1.7 or later, where this vulnerability is fixed. No other mitigations are indicated by the vendor advisory. Patch status is confirmed by the fixed version 2.1.7.

Description

Velocity.js, a JavaScript implementation of the Apache Velocity template engine, contains a critical code injection vulnerability (CWE-94) prior to version 2.1.7. The vulnerability arises because property-read expressions were not properly filtered, allowing attacker-controlled templates to access the JavaScript Function constructor via constructor.constructor. This flaw enables execution of arbitrary code, including shell commands and access to sensitive environment variables and credentials. The issue is fixed in version 2.1.7.

References

Community reviews

Loading reviews…