Skip to main content
VulnerabilityPublished Updated

CVE-2026-69222: harttle liquidjs · Uncontrolled Resource Consumption

Affects harttle liquidjsSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 10.27.2 soon.

Data as of 16 Nov 2026, 20:25 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 50% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 10.27.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Aug 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 16 Nov 2026.

What to do

Upgrade liquidjs and harttle/liquidjs to 10.27.2.

Affected software

ProductAffectedFixed in
harttleliquidjsAffected
  • <10.27.2
Fixed in
  • 10.27.2
npmharttle/liquidjspkg:npm/harttle/liquidjsOther threatsAffected
  • <10.27.2
Fixed in
  • 10.27.2

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.2 or later, where this vulnerability is fixed. No other mitigation is required as the fix addresses the root cause.

Description

CVE-2026-69222 is a high-severity vulnerability in harttle liquidjs, a JavaScript template engine. Prior to version 10.27.2, certain filters (join and array_to_sentence_string) incorrectly calculate resource usage, allowing crafted templates to cause excessive memory consumption. This can lead to process crashes due to exceeding memory limits. The issue is fixed in version 10.27.2.

References

Community reviews

Loading reviews…