CVE-2026-73649

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 59% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
75(Attend)
EG Risk 75/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
1%
EPSS %ILE
41%
KEV
Not listed

Published

August 13, 2026

Last Modified

August 14, 2026

Advisory Details (3)

Auto-updated Aug 21, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_pr, github.
github Patch Available🟡 PoC Available

Remote Code Execution via property-read to Function constructor (bypass of GHSA-j658-c2gf-x6pq fix) · Advisory · shepherdwind/velocity.js · GitHub

https://github.com/shepherdwind/velocity.js/security/advisories/GHSA-7gfh-x38p-prh3
github_pr

Guard prototype chain access to prevent prototype pollution

Fix merged in shepherdwind/velocity.js PR #192 on 2026-07-15 — awaiting tagged release

https://github.com/shepherdwind/velocity.js/pull/192
github_commit

commit f8e47a6c4607 (shepherdwind/velocity.js)

Fix landed in shepherdwind/velocity.js commit f8e47a6c4607 — awaiting tagged release

https://github.com/shepherdwind/velocity.js/commit/f8e47a6c4607249b9c967d3a1ced959b4dd64dba

Vendor Advisories for CVE-2026-73649(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
velocityjs—2.1.7—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 31× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-26 18:43 UTCEG score recompute
  2. 2026-08-26 14:47 UTCEPSS rescore
  3. 2026-08-25 15:19 UTCEG score recompute
  4. 2026-08-25 13:49 UTCEPSS rescore
  5. 2026-08-24 17:14 UTCEG score recompute
  6. 2026-08-24 12:16 UTCEG score recompute
  7. 2026-08-23 01:17 UTCEG score recompute
  8. 2026-08-23 00:19 UTCEPSS rescore
  9. 2026-08-22 03:26 UTCEG score recompute
  10. 2026-08-21 23:49 UTCEPSS rescore
  11. 2026-08-21 01:11 UTCEG score recompute
  12. 2026-08-20 22:56 UTCEPSS rescore
  13. 2026-08-19 18:27 UTCEG score recompute
  14. 2026-08-19 17:04 UTCEPSS rescore
  15. 2026-08-18 15:02 UTCEG score recompute
  16. 2026-08-18 13:49 UTCEPSS rescore
  17. 2026-08-18 13:49 UTCEPSS rescore
  18. 2026-08-17 15:36 UTCEG score recompute
  19. 2026-08-17 13:47 UTCEPSS rescore
  20. 2026-08-16 17:45 UTCEG score recompute
  21. 2026-08-16 14:56 UTCEPSS rescore
  22. 2026-08-16 14:56 UTCEPSS rescore
  23. 2026-08-16 04:38 UTCEG score recompute
  24. 2026-08-16 02:15 UTCEPSS rescore
  25. 2026-08-15 02:18 UTCEG score recompute
Show 6 more
  1. 2026-08-15 01:31 UTCEPSS rescore
  2. 2026-08-14 17:34 UTCEG score recompute
  3. 2026-08-14 17:07 UTCEG score recompute
  4. 2026-08-13 18:18 UTCEG score recompute
  5. 2026-08-13 18:12 UTCEG score recompute
  6. 2026-08-13 18:11 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-73649?
CVE-2026-73649 is a critical vulnerability published on August 13, 2026. 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…
When was CVE-2026-73649 disclosed?
CVE-2026-73649 was first published in the National Vulnerability Database on August 13, 2026, with the most recent update on August 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-73649 actively exploited?
CVE-2026-73649 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 59.3% of all scored CVEs.
What is the CVSS score of CVE-2026-73649?
CVE-2026-73649 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-73649?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-73649, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-73649

Explore →

Is Your Infrastructure Affected by CVE-2026-73649?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs