Skip to main content
VulnerabilityPublished

CVE-2026-45017: jg-rp liquid · Path Traversal

Affects jg-rp liquidSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.2 High : upgrade to 2.2.0 soon.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 4.0 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.2.0
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade jg-rp liquid to 2.2.0.

Affected software

ProductAffectedFixed in
jg-rpliquidAffected
  • <2.2.0
Fixed in
  • 2.2.0
PyPIliquidpkg:pypi/liquidOther threatsAffected
  • <2.2.0
Fixed in
  • 2.2.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

This vulnerability is fixed in Python Liquid version 2.2.0. Users should upgrade to version 2.2.0 or later to remediate this issue. Patch status is not explicitly confirmed beyond the fix in version 2.2.0; users should verify with the vendor advisory for the latest remediation guidance.

Description

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.

References

Community reviews

Loading reviews…