Skip to main content
VulnerabilityPublished Updated

CVE-2026-106120: harttle liquidjs · Information Exposure

Affects harttle liquidjsSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.0 Medium : upgrade to 10.27.2 when convenient.

Data as of 20 Nov 2026, 17:34 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Oct 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.2.

Affected software

ProductAffectedFixed in
harttleliquidjsAffected
  • <10.27.2
Fixed in
  • 10.27.2
npmliquidjspkg:npm/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 LiquidJS to version 10.27.2 or later, where this vulnerability is fixed. No other mitigation is indicated or required.

Description

CVE-2026-106120 is a vulnerability in the LiquidJS template engine where the ownPropertyOnly setting does not fully prevent access to inherited array elements through certain operations like negative indexing and filters. This can lead to exposure of sensitive information from prototype-inherited data. The issue is fixed in version 10.27.2.

References

Community reviews

Loading reviews…