sqlparse is a non-validating SQL parser module for Python. Prior to 0.6.0, group_comments in sqlparse/engine/grouping.py repeatedly rescans comment-only statements before the MAX_GROUPING_TOKENS guard, causing quadratic CPU consumption through sqlparse.parse() and sqlparse.format(sql, strip_comments=True). This issue is fixed in version 0.6.0.
CVE-2026-71491
This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 82% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.7
- EG Score
- 8.7(medium)
- EG Risk
- 54(Track)EG Risk 54/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity87% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 18%
- KEV
- Not listed
Published
August 17, 2026
Last Modified
August 17, 2026
Advisory Details (2)
Auto-updated Aug 17, 2026commit ef2012a5eeb4 (andialbrecht/sqlparse)
Fix landed in andialbrecht/sqlparse commit ef2012a5eeb4 — awaiting tagged release
https://github.com/andialbrecht/sqlparse/commit/ef2012a5eeb491e604dea2b00d516904a3830c87Quadratic O(n²) DoS in group_comments · Advisory · andialbrecht/sqlparse · GitHub
https://github.com/andialbrecht/sqlparse/security/advisories/GHSA-f2ff-p2ww-7p4pVendor Advisories for CVE-2026-71491(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 11× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-19 22:38 UTCEG score recompute
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 22:29 UTCEG score recompute
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-17 22:22 UTCEG score recompute
- 2026-08-17 22:09 UTCEG score recompute
- 2026-08-17 18:29 UTCEG score recompute
- 2026-08-17 17:30 UTCEG score recompute
- 2026-08-17 17:29 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-71491?
When was CVE-2026-71491 disclosed?
Is CVE-2026-71491 actively exploited?
What is the CVSS score of CVE-2026-71491?
How do I remediate CVE-2026-71491?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-71491
Is Your Infrastructure Affected by CVE-2026-71491?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.