Skip to main content
VulnerabilityPublished Updated

CVE-2026-55865: jg-rp liquid · Infinite Loop

Affects jg-rp liquidSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.1 High : upgrade to 2.2.1 soon.

Data as of 21 Nov 2026, 17:35 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Jul 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 21 Nov 2026.

What to do

Upgrade jg-rp liquid to 2.2.1.

Affected software

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

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

AI-suggested

Upgrade to Python Liquid version 2.2.1 or later, where this infinite loop issue is fixed. Patch status is confirmed by the versioning information indicating the fix in 2.2.1. No other mitigations are specified or required.

Description

Python Liquid is a Python engine for the Liquid template language. Prior to 2.2.1, given a malformed {% case %} tag without an associated {% when %} or {% else %} block and no terminating {% endcase %} tag, Python Liquid hangs in an infinite loop at parse time because liquid.TokenStream.eof did not give the EOF token matching kind and value fields, allowing malicious template authors to craft templates for a denial of service attack. This issue is fixed in version 2.2.1.

References

Community reviews

Loading reviews…