CVE-2026-44645

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreMEDIUM confidence

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

Score 6.5 from GitHub Security Advisory published 2026-05-27. A secondary CVSS source baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-37822 (ENISA EUVD) · GHSA-8xx9-69p8-7jp3 (GitHub Security Advisories)Source: ENISA EUVD

6.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (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.4%CVSS: 6.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

LiquidJS is a Shopify/GitHub Pages compatible template engine written in pure JavaScript. In versions 10.25.7 and below, the renderLimit option can be fully bypassed by a {% for %} (or {% tablerow %}) tag whose body is empty. The renderLimit option is documented in docs/source/tutorials/dos.md as the mechanism that "mitigates this by limiting the time consumed by each render() call." The per-iteration time check is reached only when the body contains at least one template node, so a template such as {%- for i in (1..N) -%}{%- endfor -%} iterates the full collection without ever consulting renderLimit. With a configured renderLimit of 50 ms, a single parseAndRenderSync call has been observed to consume 2.26 seconds (~45× over the limit) and scales linearly with N up to memoryLimit, allowing a low-privileged template author to wedge an event-loop thread for an attacker-chosen duration. Deployments that rely on a finite renderLimit for DoS protection (common in multi-tenant template-authoring environments) can still be forced by a single crafted template to monopolize a Node.js event-loop worker for attacker-controlled time, potentially stalling in-flight requests, with availability impact only. This issue has been fixed in version 10.26.0.

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
45
EG Risk 45/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)
Severity65% × 45%
Impact severity (EG Severity): CVSS 6.5 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.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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.
EPSS PROB
0.4%
EPSS %ILE
32nd
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 (6.5): severity, escalated by confirmed exploitation. This CVE's 6.5 is its impact severity (EG Severity), not escalated.

EG Severity
6.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS. 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 or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (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

May 27, 2026

Last Modified

October 25, 2026

Advisory Details (3)

Auto-updated Jun 17, 2026
Patch available. Sources: github_commit, github_release, github.
GitHub advisoryMentions a patch (unverified)

renderLimit DoS guard bypass via empty `{% for %}` body in liquidjs · Advisory · harttle/liquidjs · GitHub

https://github.com/harttle/liquidjs/security/advisories/GHSA-8xx9-69p8-7jp3
GitHub release Patch Available

v10.26.0

Patch available: harttle/liquidjs v10.26.0

https://github.com/harttle/liquidjs/releases/tag/v10.26.0
GitHub commit Patch Available

commit 5b9c3469085e (harttle/liquidjs)

Patch available: harttle/liquidjs v10.26.0 (contains commit 5b9c3469085e)

https://github.com/harttle/liquidjs/commit/5b9c3469085e01c79e2d0af28e2a13f730e1793d

Vendor Advisories for CVE-2026-44645(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
npmliquidjs—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
liquidjs—
  • every version through 10.25.7: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 39× 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 it from the CNA feed. 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). Most recent first.

Showing the most recent 100 of 202 refreshes 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 102 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-44645?
CVE-2026-44645 is a medium-severity vulnerability; its CVE record was published on May 27, 2026. LiquidJS is a Shopify/GitHub Pages compatible template engine written in pure JavaScript. In versions 10.25.7 and below, the renderLimit option can be fully bypassed by a {% for %} (or {% tablerow %}) tag whose body is empty. The renderLimit option is documented in docs/source/tutorials/dos.md as…
When was the CVE record for CVE-2026-44645 published?
The CVE record for CVE-2026-44645 was published on May 27, 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 25, 2026; the record at its source may have been updated since.
Is CVE-2026-44645 actively exploited?
CVE-2026-44645 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (32nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-44645?
CVE-2026-44645 has a CVSS base score of 6.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-44645?
A fix for CVE-2026-44645 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-44645 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-44645

Explore →

Is Your Infrastructure Affected by CVE-2026-44645?

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

Book a Demo →Browse All CVEs