CVE-2026-73649

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-24. A secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated

Also known asEUVD-2026-58192 (ENISA EUVD) · GHSA-7gfh-x38p-prh3 (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.8CRITICALmedium confidence
EG Risk
75
EG Risk 75/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.7%
EPSS %ILE
54th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 13, 2026

Last Modified

October 24, 2026

Advisory Details (3)

Auto-updated Nov 7, 2026
Patch available. Sources: github, github_commit, github_pr.
GitHub advisoryMentions a patch (unverified)

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 pull request

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.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmvelocityjs @ 2.1.7 (fixes <= 2.1.6)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
velocityjs—
  • every version up to 2.1.7: fixed in 2.1.7
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 16× in last 7d / 44× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 189 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 89 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 06:27 UTCEchelonGraph re-scored
  2. 2026-11-13 06:27 UTCGHSA enrichmentGHSA-7gfh-x38p-prh3 · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  4. 2026-11-12 08:04 UTCEchelonGraph re-scored
  5. 2026-11-12 08:04 UTCGHSA enrichmentGHSA-7gfh-x38p-prh3 · GitHub severity CRITICAL · GitHub CVSS 9.8
  6. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  7. 2026-11-11 09:40 UTCEchelonGraph re-scored
  8. 2026-11-11 09:40 UTCGHSA enrichmentGHSA-7gfh-x38p-prh3 · GitHub severity CRITICAL · GitHub CVSS 9.8
  9. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  10. 2026-11-10 11:18 UTCEchelonGraph re-scored
  11. 2026-11-10 11:18 UTCGHSA enrichmentGHSA-7gfh-x38p-prh3 · GitHub severity CRITICAL · GitHub CVSS 9.8
  12. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  13. 2026-11-09 12:55 UTCEchelonGraph re-scored
  14. 2026-11-09 12:55 UTCGHSA enrichmentGHSA-7gfh-x38p-prh3 · GitHub severity CRITICAL · GitHub CVSS 9.8
  15. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  16. 2026-11-08 14:33 UTCEchelonGraph re-scored
  17. 2026-11-08 14:33 UTCGHSA enrichmentGHSA-7gfh-x38p-prh3 · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  19. 2026-11-07 16:11 UTCGHSA enrichmentGHSA-7gfh-x38p-prh3 · GitHub severity CRITICAL · GitHub CVSS 9.8
  20. 2026-11-06 17:45 UTCEchelonGraph re-scored
  21. 2026-11-06 17:45 UTCGHSA enrichmentGHSA-7gfh-x38p-prh3 · GitHub severity CRITICAL · GitHub CVSS 9.8
  22. 2026-11-06 17:25 UTCOSV refresh
  23. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  24. 2026-11-05 19:23 UTCEchelonGraph re-scored
  25. 2026-11-05 19:23 UTCGHSA enrichmentGHSA-7gfh-x38p-prh3 · GitHub severity CRITICAL · GitHub CVSS 9.8
Show 75 more
  1. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  2. 2026-11-04 21:01 UTCEchelonGraph re-scored
  3. 2026-11-04 21:01 UTCGHSA enrichmentGHSA-7gfh-x38p-prh3 · GitHub severity CRITICAL · GitHub CVSS 9.8
  4. 2026-11-04 16:36 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  5. 2026-11-03 22:38 UTCEchelonGraph re-scored
  6. 2026-11-03 22:38 UTCGHSA enrichmentGHSA-7gfh-x38p-prh3 · GitHub severity CRITICAL · GitHub CVSS 9.8
  7. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  8. 2026-11-03 00:13 UTCEchelonGraph re-scored
  9. 2026-11-03 00:13 UTCGHSA enrichmentGHSA-7gfh-x38p-prh3 · GitHub severity CRITICAL · GitHub CVSS 9.8
  10. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  11. 2026-11-02 01:48 UTCEchelonGraph re-scored
  12. 2026-11-02 01:48 UTCGHSA enrichmentGHSA-7gfh-x38p-prh3 · GitHub severity CRITICAL · GitHub CVSS 9.8
  13. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  14. 2026-11-01 07:39 UTCGHSA enrichmentGHSA-7gfh-x38p-prh3 · GitHub severity CRITICAL · GitHub CVSS 9.8
  15. 2026-11-01 07:39 UTCEchelonGraph re-scored
  16. 2026-11-01 03:26 UTCEchelonGraph re-scored
  17. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  18. 2026-10-31 05:03 UTCEchelonGraph re-scored
  19. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  20. 2026-10-30 06:40 UTCEchelonGraph re-scored
  21. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  22. 2026-10-29 08:19 UTCEchelonGraph re-scored
  23. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  24. 2026-10-28 09:56 UTCEchelonGraph re-scored
  25. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  26. 2026-10-27 10:40 UTCEchelonGraph re-scored
  27. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  28. 2026-10-26 12:18 UTCEchelonGraph re-scored
  29. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  30. 2026-10-25 13:50 UTCEchelonGraph re-scored
  31. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  32. 2026-10-23 18:26 UTCEchelonGraph re-scored
  33. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  34. 2026-10-23 01:31 UTCEchelonGraph re-scored
  35. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  36. 2026-10-22 02:51 UTCEchelonGraph re-scored
  37. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  38. 2026-10-21 04:21 UTCEchelonGraph re-scored
  39. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  40. 2026-10-20 05:58 UTCEchelonGraph re-scored
  41. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  42. 2026-10-19 07:32 UTCEchelonGraph re-scored
  43. 2026-10-18 03:15 UTCEchelonGraph re-scored
  44. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  45. 2026-10-17 10:43 UTCEchelonGraph re-scored
  46. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  47. 2026-10-16 12:16 UTCEchelonGraph re-scored
  48. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  49. 2026-10-15 13:49 UTCEchelonGraph re-scored
  50. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  51. 2026-10-14 08:44 UTCEchelonGraph re-scored
  52. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  53. 2026-10-13 04:07 UTCEchelonGraph re-scored
  54. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  55. 2026-10-12 15:40 UTCEchelonGraph re-scored
  56. 2026-10-11 19:26 UTCEchelonGraph re-scored
  57. 2026-10-11 16:42 UTCEchelonGraph re-scored
  58. 2026-10-11 14:01 UTCEchelonGraph re-scored
  59. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  60. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  61. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  62. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  63. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  64. 2026-10-06 17:41 UTCEchelonGraph re-scored
  65. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  66. 2026-10-05 18:59 UTCEchelonGraph re-scored
  67. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  68. 2026-10-05 02:40 UTCEchelonGraph re-scored
  69. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  70. 2026-10-03 19:47 UTCEchelonGraph re-scored
  71. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  72. 2026-10-02 21:52 UTCEchelonGraph re-scored
  73. 2026-10-02 07:32 UTCEchelonGraph re-scored
  74. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  75. 2026-09-30 21:46 UTCEchelonGraph re-scored

Related CVEs(same product + same CWE)

Same product

1 shown

npm:velocityjs

Frequently asked(5)

What is CVE-2026-73649?
CVE-2026-73649 is a critical-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-73649 published?
The CVE record for CVE-2026-73649 was published on August 13, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 24, 2026; the record at its source may have been updated since.
Is CVE-2026-73649 actively exploited?
CVE-2026-73649 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (54th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-73649?
CVE-2026-73649 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-73649?
A fix for CVE-2026-73649 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-73649 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs