CVE-2026-71491Public exploitNetwork attack vector

CPU exhaustion via comment-tail rescanning

Published Aug 17, 2026 · Updated Aug 17, 2026

Denial of service in sqlparse before 0.6.0 allows attackers to cause excessive CPU consumption via comment-only SQL statements. The group_comments function in sqlparse/engine/grouping.py rescans the remaining comment and newline token tail for each comment before the MAX_GROUPING_TOKENS guard, so sqlparse.parse() and sqlparse.format(sql, strip_comments=True) perform quadratic work on comment-only input. Exposure requires an attacker-controlled SQL string to reach code that parses or strips comments with sqlparse; the result is a hang or severe slowdown rather than code execution or data access.

CVSS severity8.7
High
EPSS probability0.26%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Denial of service in sqlparse before 0.6.0 allows attackers to cause excessive CPU consumption via comment-only SQL statements. The group_comments function in sqlparse/engine/grouping.py rescans the remaining comment and newline token tail for each comment before the MAX_GROUPING_TOKENS guard, so sqlparse.parse() and sqlparse.format(sql, strip_comments=True) perform quadratic work on comment-only input. Exposure requires an attacker-controlled SQL string to reach code that parses or strips comments with sqlparse; the result is a hang or severe slowdown rather than code execution or data access.

The record

CVE
CVE-2026-71491
Published
Aug 17, 2026
Updated
Aug 17, 2026
Vendor
Andi Albrecht
Product
sqlparse
Classifications
CWE-400, CWE-407, T1499
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Aug 17, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 17, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 0.6.0

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Andi Albrecht · sqlparseversion=< 0.6.0

Published CVSS scores

8.7GitHubCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-400Uncontrolled Resource Consumption
CWE-407Inefficient Algorithmic Complexity
T1499Endpoint Denial of Service

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo