CVE-2026-61556

HIGHPre-NVD 8.78.7
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (44th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-63089 (ENISA EUVD) · GHSA-m7fp-h3p4-hr49 (GitHub Security Advisories)Source: ENISA EUVD

8.7EG
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.5%CVSS: 8.7Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

LiquidJS is a Shopify / GitHub Pages compatible template engine in pure JavaScript. From 10.26.0 until 10.27.1, the strip_html filter in src/filters/html.ts can enter an infinite loop when an input string contains <, includes at least one preceding character, and has no later >. In strip_html, the search for the next opener advances lt while the loop index remains unchanged when the closer search returns -1, and the equality-only stall guard does not exit because the loop index is less than lt. Reprocessing the same state indefinitely blocks template rendering and can cause denial of service with an input as short as a<. This issue is fixed in version 10.27.1.

CVSS v3
8.7
EG Score
8.7HIGHmedium confidence
EG Risk
70
EG Risk 70/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)
Severity87% × 45%
Impact severity (EG Severity): CVSS 8.7 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 or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
44th
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 (8.7): severity, escalated by confirmed exploitation. This CVE's 8.7 is its impact severity (EG Severity), not escalated.

EG Severity
8.7 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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; Attend at high (mission-essential systems).CISA BOD 26-04: 14 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 or medium mission impact; Attend at high (mission-essential systems).

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 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)14 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 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

August 19, 2026

Last Modified

September 9, 2026

Advisory Details (4)

Auto-updated Aug 19, 2026
Patch available. Sources: github_release, github, github_pr, github_commit.
GitHub release Patch Available

v10.27.1

Patch available: harttle/liquidjs v10.27.1

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

commit 5c3522f33928 (harttle/liquidjs)

Patch available: harttle/liquidjs v10.27.1 (contains commit 5c3522f33928)

https://github.com/harttle/liquidjs/commit/5c3522f33928aae66f0fe85c36e1d9015c768fe2
GitHub pull request Patch Available

fix(strip_html): avoid infinite loop on unclosed openers

Patch available: harttle/liquidjs v10.27.1 (PR #917 merged 2026-06-21)

https://github.com/harttle/liquidjs/pull/917
GitHub advisoryMentions a patch (unverified)

An infinite loop vulnerability in `strip_html` filter · Advisory · harttle/liquidjs · GitHub

https://github.com/harttle/liquidjs/security/advisories/GHSA-m7fp-h3p4-hr49

Vendor Advisories for CVE-2026-61556(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 @ 10.27.1 (fixes >= 10.26.0, < 10.27.1)—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—
  • 10.26.0 up to 10.27.1: fixed in 10.27.1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 46× 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 119 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 19 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-61556?
CVE-2026-61556 is a high-severity vulnerability; its CVE record was published on August 19, 2026. LiquidJS is a Shopify / GitHub Pages compatible template engine in pure JavaScript. From 10.26.0 until 10.27.1, the strip_html filter in src/filters/html.ts can enter an infinite loop when an input string contains <, includes at least one preceding character, and has no later >. In strip_html, the…
When was the CVE record for CVE-2026-61556 published?
The CVE record for CVE-2026-61556 was published on August 19, 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 September 9, 2026; the record at its source may have been updated since.
Is CVE-2026-61556 actively exploited?
CVE-2026-61556 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-61556?
CVE-2026-61556 has a CVSS base score of 8.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-61556?
A fix for CVE-2026-61556 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-61556 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-61556

Explore →

Is Your Infrastructure Affected by CVE-2026-61556?

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