What is CVE-2026-55865?

CVE-2026-55865 is a medium-severity security vulnerability in python-liquid (pip), affecting versions < 2.2.1. It is fixed in 2.2.1.

Which versions of python-liquid are affected by CVE-2026-55865?

python-liquid (pip) versions < 2.2.1 is affected.

Is there a fix for CVE-2026-55865?

Yes. CVE-2026-55865 is fixed in 2.2.1. Upgrade to this version or later.

Is CVE-2026-55865 exploitable, and should I be worried?

Whether CVE-2026-55865 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-55865 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-55865?

Upgrade python-liquid to 2.2.1 or later.

CVE-2026-55865 in python-liquid | Intelligent Application Security

Q: Which versions of python-liquid are affected by CVE-2026-55865?

python-liquid (pip) versions < 2.2.1 is affected.

Q: Is there a fix for CVE-2026-55865?

Yes. CVE-2026-55865 is fixed in 2.2.1. Upgrade to this version or later.

Q: Is CVE-2026-55865 exploitable, and should I be worried?

Whether CVE-2026-55865 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-55865 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-55865?

Upgrade python-liquid to 2.2.1 or later.

Summary

Workarounds

Manually correct the definition of liquid.TokenStream.eof before parsing any templates.

import liquid
from liquid.token import TOKEN_EOF

liquid.stream.TokenStream.eof = liquid.Token(TOKEN_EOF, TOKEN_EOF, -1, "")

# ...

Impact

Given a malformed {% case %} tag without associated {% when %} or {% else %} block, and no terminating {% endcase %} tag, Python Liquid hangs in an infinite loop at parse time. This allows malicious template authors to craft templates for a denial of service attack.

Affected versions

python-liquid (< 2.2.1)

Security releases

python-liquid → 2.2.1 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

See it in your environment

Remediation advice

The issue is fixed in version 2.2.1 with the correction of the liquid.TokenStream.eof attribute. The kind and value of the special EOF token are now the same, so either can be tested against liquid.token.TOKEN_EOF.

Frequently Asked Questions

What is CVE-2026-55865? CVE-2026-55865 is a medium-severity security vulnerability in python-liquid (pip), affecting versions < 2.2.1. It is fixed in 2.2.1.
Which versions of python-liquid are affected by CVE-2026-55865? python-liquid (pip) versions < 2.2.1 is affected.
Is there a fix for CVE-2026-55865? Yes. CVE-2026-55865 is fixed in 2.2.1. Upgrade to this version or later.
Is CVE-2026-55865 exploitable, and should I be worried? Whether CVE-2026-55865 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-55865 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-55865? Upgrade python-liquid to 2.2.1 or later.

Other vulnerabilities in python-liquid

CVE-2026-55865