What is GHSA-27JP-WM6Q-GP25?

GHSA-27JP-WM6Q-GP25 is a medium-severity allocation of resources without limits or throttling vulnerability in sqlparse (pip), affecting versions <= 0.5.3. It is fixed in 0.5.4. The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap.

Which versions of sqlparse are affected by GHSA-27JP-WM6Q-GP25?

sqlparse (pip) versions <= 0.5.3 is affected.

Is there a fix for GHSA-27JP-WM6Q-GP25?

Yes. GHSA-27JP-WM6Q-GP25 is fixed in 0.5.4. Upgrade to this version or later.

Is GHSA-27JP-WM6Q-GP25 exploitable, and should I be worried?

Whether GHSA-27JP-WM6Q-GP25 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 GHSA-27JP-WM6Q-GP25 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.

GHSA-27JP-WM6Q-GP25 in sqlparse

Q: Which versions of sqlparse are affected by GHSA-27JP-WM6Q-GP25?

sqlparse (pip) versions <= 0.5.3 is affected.

Q: Is there a fix for GHSA-27JP-WM6Q-GP25?

Yes. GHSA-27JP-WM6Q-GP25 is fixed in 0.5.4. Upgrade to this version or later.

Q: Is GHSA-27JP-WM6Q-GP25 exploitable, and should I be worried?

Whether GHSA-27JP-WM6Q-GP25 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 GHSA-27JP-WM6Q-GP25 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 GHSA-27JP-WM6Q-GP25?

Upgrade sqlparse to 0.5.4 or later.

Summary

sqlparse: formatting list of tuples leads to denial of service

The below gist hangs while attempting to format a long list of tuples.

This was found while drafting a regression test for Dja
ngo 5.2's composite primary key feature, which allows querying composite fields with tuples.

Impact

The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap. Typical impact: resource exhaustion leading to denial of service.

Affected versions

sqlparse (<= 0.5.3)

Security releases

sqlparse → 0.5.4 (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.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade sqlparse to 0.5.4 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is GHSA-27JP-WM6Q-GP25? GHSA-27JP-WM6Q-GP25 is a medium-severity allocation of resources without limits or throttling vulnerability in sqlparse (pip), affecting versions <= 0.5.3. It is fixed in 0.5.4. The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap.
Which versions of sqlparse are affected by GHSA-27JP-WM6Q-GP25? sqlparse (pip) versions <= 0.5.3 is affected.
Is there a fix for GHSA-27JP-WM6Q-GP25? Yes. GHSA-27JP-WM6Q-GP25 is fixed in 0.5.4. Upgrade to this version or later.
Is GHSA-27JP-WM6Q-GP25 exploitable, and should I be worried? Whether GHSA-27JP-WM6Q-GP25 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 GHSA-27JP-WM6Q-GP25 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 GHSA-27JP-WM6Q-GP25? Upgrade sqlparse to 0.5.4 or later.

Other vulnerabilities in sqlparse

CVE-IDSeverityPackage summary

CVE-2024-4340Highsqlparse: sqlparse parsing heavily nested list leads to Denial of Service CVE-2023-30608Mediumsqlparse: sqlparse contains a regular expression that is vulnerable to Regular Expression Denial of Service CVE-2021-32839Highsqlparse: StripComments filter contains a regular expression that is vulnerable to ReDOS (Regular Expression Denial of Service)