Python LiquidApplication · Jg Rp
CVE-2026-45017
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedPython 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidencePython Liquid versions before 2.2.0 contain a path traversal vulnerability in FileSystemLoader and CachingFileSystemLoader. The loaders fail to guard against absolute paths in {% include %} and {% render %} tags, allowing attackers to read arbitrary readable files containing valid Liquid markup.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Python LiquidApplication
< 2.2.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check the installed Python Liquid versionRun `pip show python-liquid` or check your dependency lock file for the python-liquid package versionAffected if The version is lower than 2.2.0
-
Identify if FileSystemLoader is in useSearch your codebase for imports or instantiations of `FileSystemLoader` or `CachingFileSystemLoader` from the `liquid` moduleAffected if Either loader class is imported and used in your application
-
Determine if include/render tags accept external inputReview code that handles {% include %} or {% render %} tag arguments. Check if template names or paths come from user request parameters, API input, or any untrusted sourceAffected if Template paths in include/render tags can be controlled by external users or derived from untrusted input
-
Audit template files for include/render usageSearch template files for {% include %} and {% render %} tag patterns, noting which variables are passed as the template sourceAffected if Templates use dynamic variable names in include/render tags without validation
You are affected if Python Liquid is below version 2.2.0 AND your application uses FileSystemLoader or CachingFileSystemLoader with {% include %} or {% render %} tags that accept unvalidated external input for template paths.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.2.0
Upgrade Python Liquid to version 2.2.0 or later to obtain the patch that adds path traversal protection to the filesystem loaders.
2.2.0
- Check the currently installed version of python-liquid by running: pip show python-liquid or pip freeze | grep -i liquid
- Upgrade to the fixed version by running: pip install python-liquid==2.2.0
- Verify the upgrade was successful by checking the installed version: pip show python-liquid
- If using a requirements file, update the version constraint to: python-liquid>=2.2.0
- After upgrading, test that the FileSystemLoader and CachingFileSystemLoader properly restrict file access to their configured search paths to confirm the vulnerability is mitigated
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Python Liquid
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-45017 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-45017 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data