CVE-2026-55575: CWE-770: Allocation of Resources Without Limits or Throttling in harttle liquidjs
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.
AI Analysis
Technical Summary
LiquidJS, a JavaScript template engine compatible with Shopify and GitHub Pages, contained a resource allocation vulnerability (CWE-770) in versions before 10.27.1. Specifically, the pop array filter at src/filters/array.ts cloned its input array using [...toArray(v)] without invoking this.context.memoryLimit.use(...), thus bypassing memory usage limits. This flaw allows a template render such as {{ huge_array | pop }} to allocate an O(N) clone of an attacker-influenced array outside the configured memory budget, potentially causing denial of service due to excessive memory consumption. The issue is resolved in version 10.27.1.
Potential Impact
An attacker can cause the application to allocate large amounts of memory by rendering templates that use the vulnerable pop filter on large arrays. This uncontrolled memory allocation can lead to denial of service conditions by exhausting system memory resources. There is no indication of privilege escalation or code execution from the provided data.
Mitigation Recommendations
Upgrade to liquidjs version 10.27.1 or later, where this vulnerability is fixed. No other mitigation or temporary workaround is indicated in the available data.
CVE-2026-55575: CWE-770: Allocation of Resources Without Limits or Throttling in harttle liquidjs
Description
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 v4.0
Score 8.2high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
LiquidJS, a JavaScript template engine compatible with Shopify and GitHub Pages, contained a resource allocation vulnerability (CWE-770) in versions before 10.27.1. Specifically, the pop array filter at src/filters/array.ts cloned its input array using [...toArray(v)] without invoking this.context.memoryLimit.use(...), thus bypassing memory usage limits. This flaw allows a template render such as {{ huge_array | pop }} to allocate an O(N) clone of an attacker-influenced array outside the configured memory budget, potentially causing denial of service due to excessive memory consumption. The issue is resolved in version 10.27.1.
Potential Impact
An attacker can cause the application to allocate large amounts of memory by rendering templates that use the vulnerable pop filter on large arrays. This uncontrolled memory allocation can lead to denial of service conditions by exhausting system memory resources. There is no indication of privilege escalation or code execution from the provided data.
Mitigation Recommendations
Upgrade to liquidjs version 10.27.1 or later, where this vulnerability is fixed. No other mitigation or temporary workaround is indicated in the available data.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-06-16T23:11:20.214Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a4ea886c9d9e3dbe3a52513
Added to database: 07/08/2026, 19:44:06 UTC
Last enriched: 07/16/2026, 10:11:20 UTC
Last updated: 08/22/2026, 10:52:10 UTC
Views: 72
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.