Path Traversal in python-liquid (CVE-2026-45017)
Summary
Path traversal in python-liquid (CVE-2026-45017). Confidential information can be exposed externally. Exploitable via FileSystemLoader. Mitigation: upgrade to 2.2.0 or later.
Original description
The description as published by the source.
Python Liquid is a Python engine for the Liquid template language. Prior to 2.2.0, the built-in FileSystemLoader and CachingFileSystemLoader do not guard against reading files outside their search paths when given an absolute path to resolve. This allows malicious template authors to load and render arbitrary files via the {% include %} and {% render %} tags. Targeted files would need to contain valid Liquid markup and be readable by the application process. This vulnerability is fixed in 2.2.0.
Source: GitHub Security Advisories (Global) 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-45017 has been found in python-liquid.
Attackers can target a specific entry point like FileSystemLoader over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.5/10.
What to do: upgrade python-liquid to 2.2.0 or later.
If unsure, ask your IT team or search "python-liquid CVE-2026-45017" on the vendor's site.
CVE-2026-45017 (python-liquid) — CWE-22 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: FileSystemLoader / CachingFileSystemLoader / loader
Patched: 2.2.0 — 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.
Path traversal (CWE-22) exists in python-liquid. Attackers reach the vulnerable code path via FileSystemLoader without authentication.
Check the vendor advisory for the affected versions of python-liquid. Attack surface: FileSystemLoader / CachingFileSystemLoader / loader.
Severity: High (CVSS 7.5/10). Confidential information can be exposed externally.
Update to 2.2.0.
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 'python-liquid' . 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 'python-liquid' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
python-liquidを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade python-liquid to 2.2.0ステージング環境で 2.2.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com