Information Disclosure in liquidjs (CVE-2026-106120)
Summary
Vulnerability in liquidjs (CVE-2026-106120). Risk of unauthorized operations or information disclosure. Exploitable via ownPropertyOnly. Mitigation: upgrade to 10.27.2 or later.
Original description
The description as published by the source.
Summary
LiquidJS’s ownPropertyOnly option is intended to prevent templates from reading inherited or prototype properties from scope data.
With ownPropertyOnly: true, direct access such as:
{{ a[0] }}
correctly blocks an inherited array index. However, the same inherited value is still disclosed through:
.first
.last
negative indexing
for-loop iteration
first
last
join
reverse
slice
compact
Impact
This is an information disclosure issue when an application relies on ownPropertyOnly: true to safely render templates over untrusted or prototype-polluted scope data.
Object prototype property reads are blocked as expected, but inherited Array.prototype index reads are not consistently blocked. An attacker who can influence prototype state or inherited array-index data may cause templates to disclose values that ownPropertyOnly is expected to hide.
Proof of concept
const { Liquid } = require("liquidjs");
const engine = new Liquid({ ownPropertyOnly: true });
Array.prototype[0] = "ARRAY_PROTO_POLLUTED";
Object.prototype.secret = "OBJECT_PROTO_POLLUTED";
const a = [];
a.length = 1;
const o = {};
for (const [src, scope] of [
["{{ a[0] }}", { a }],
["{{ a[-1] }}", { a }],
["{{ o.secret }}", { o }],
["{{ a.first }}", { a }],
["{{ a.last }}", { a }],
["{{ a | first }}", { a }],
["{{ a | last }}", { a }],
["{{ a | join: ',' }}", { a }],
["{{ a | reverse | first }}", { a }],
["{{ a | slice: 0, 1 | join: ',…
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-106120 has been found in liquidjs.
Attackers can target a specific entry point like ownPropertyOnly over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade liquidjs to 10.27.2 or later.
If unsure, ask your IT team or search "liquidjs CVE-2026-106120" on the vendor's site.
CVE-2026-106120 (liquidjs) — CWE-200
Attack surface: ownPropertyOnly / Array.prototype
Patched: 10.27.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Information disclosure (CWE-200) exists in liquidjs. Attackers reach the vulnerable code path via ownPropertyOnly.
Check the vendor advisory for the affected versions of liquidjs. Attack surface: ownPropertyOnly / Array.prototype.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 10.27.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'liquidjs' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'liquidjs' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
liquidjsを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade liquidjs to 10.27.2ステージング環境で 10.27.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。