Skip to main content
VulnerabilityPublished

CVE-2026-55575: harttle liquidjs · Unthrottled Resource Allocation

Affects harttle liquidjsSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.2 High : upgrade to 10.27.1 soon.

Data as of 20 Nov 2026, 17:35 UTC

CVSS 4.0 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 10.27.1
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.

What to do

Upgrade harttle liquidjs to 10.27.1.

Affected software

ProductAffectedFixed in
harttleliquidjsAffected
  • <10.27.1
Fixed in
  • 10.27.1
npmliquidjspkg:npm/liquidjsOther threatsAffected
  • <10.27.1
Fixed in
  • 10.27.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

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.

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.

References

Community reviews

Loading reviews…