CVE-2026-45017
Local file read via include/render in Python Liquid before 2.2.0.
Is CVE-2026-45017 being exploited?
Not confirmed. CVE-2026-45017 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.34% probability of exploitation in the next 30 days.
How severe is CVE-2026-45017?
CVE-2026-45017 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-45017?
Yes. A fix has been recorded for CVE-2026-45017. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-45017 affect?
CVE-2026-45017 affects Python-Liquid <= 2.1.x. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-45017?
Upgrade to 2.2.0+
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Local file disclosure via include/render with absolute paths; attacker can read arbitrary files readable by the app process.
Patch when possible
- affected< 2.2.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.