Information Disclosure in LiquidJS (CVE-2026-39412)
Summary
Vulnerability in LiquidJS (CVE-2026-39412). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 10.25.4 or later.
Original description
The description as published by the source.
LiquidJS is a Shopify / GitHub Pages compatible template engine in pure JavaScript. Prior to 10.25.4, the sort_natural filter bypasses the ownPropertyOnly security option, allowing template authors to extract values of prototype-inherited properties through a sorting side-channel attack. Applications relying on ownPropertyOnly: true as a security boundary (e.g., multi-tenant template systems) are exposed to information disclosure of sensitive prototype properties such as API keys and tokens. This vulnerability is fixed in 10.25.4.
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-39412 has been found in LiquidJS.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: upgrade LiquidJS to 10.25.4 or later.
If unsure, ask your IT team or search "LiquidJS CVE-2026-39412" on the vendor's site.
CVE-2026-39412 (LiquidJS) — CWE-200 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 10.25.4 — 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.
Check the vendor advisory for the affected versions of LiquidJS.
Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.
Update to 10.25.4.
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.25.4ステージング環境で 10.25.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- patch github.com
- patch github.com
- web github.com