CVE-2026-55575

HIGHPre-NVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (42nd percentile of EPSS-scored CVEs). 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
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.2Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

LiquidJS is a Shopify / GitHub Pages compatible template engine in pure JavaScript. Prior to 10.27.1, the pop array filter at src/filters/array.ts allocated a full clone of its input array via [...toArray(v)] without calling this.context.memoryLimit.use(...), allowing a template render such as {{ huge_array | pop }} to allocate an O(N) clone of an attacker-influenced array outside the configured memoryLimit budget. This issue is fixed in version 10.27.1.

CVSS v3
8.2
EG Score
8.2HIGHmedium confidence
EG Risk
68
EG Risk 68/100CISA SSVC

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
Severity82% × 45%
Exploitation40% × 40%
Automatability100% × 15%
CISA SSVC: Track at low, Track* at medium and Attend at high mission impact.
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
42nd
KEV
Not listed

CISA SSVCTrack 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). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

July 8, 2026

Last Modified

July 10, 2026

Advisory Details (4)

Auto-updated Jul 8, 2026
🔬 Proof of concept available. Patch available. Sources: github_release, github, github_commit, github_pr.
githubMentions a patch (unverified)🟡 PoC Available

`pop` filter bypasses `memoryLimit` accounting that its array-filter siblings enforce · Advisory · harttle/liquidjs · GitHub

https://github.com/harttle/liquidjs/security/advisories/GHSA-g357-x5c3-c72p
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_pr Patch Available

fix(security): charge pop filter allocation to memoryLimit

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

https://github.com/harttle/liquidjs/pull/907
github_commit Patch Available

commit 8a0c74a7fcb1 (harttle/liquidjs)

Patch available: harttle/liquidjs v10.27.1 (contains commit 8a0c74a7fcb1)

https://github.com/harttle/liquidjs/commit/8a0c74a7fcb1671aa1dcb71ec82ba0602dc90d04

Vendor Advisories for CVE-2026-55575(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 rangeFix by version rangeDependents
liquidjs—
  • every version 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 7× in last 7d / 33× 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.

Showing the most recent 100 of 133 total refreshes for this CVE.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-55575?
CVE-2026-55575 is a high vulnerability published on July 8, 2026. LiquidJS is a Shopify / GitHub Pages compatible template engine in pure JavaScript. Prior to 10.27.1, the pop array filter at src/filters/array.ts allocated a full clone of its input array via [...toArray(v)] without calling this.context.memoryLimit.use(...), allowing a template render such as {{…
When was CVE-2026-55575 disclosed?
CVE-2026-55575 was first published on July 8, 2026, with the most recent update on July 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55575 actively exploited?
CVE-2026-55575 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (42nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-55575?
CVE-2026-55575 has a CVSS base score of 8.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-55575?
A fix for CVE-2026-55575 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-55575 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-55575

Explore →

Is Your Infrastructure Affected by CVE-2026-55575?

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

Book a Demo →Browse All CVEs