CVE-2026-71491

HIGHPre-NVD 8.78.7—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (16th percentile of EPSS-scored CVEs). 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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — Patch released this week
8.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 8.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
8.7
EG Score
8.7HIGHmedium confidence
EG Risk
54
EG Risk 54/100CISA SSVC

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 computed
Severity87% × 45%
Exploitation0% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.3%
EPSS %ILE
16th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 17, 2026

Last Modified

September 9, 2026

Advisory Details (2)

Auto-updated Aug 17, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit.
github_commit

commit ef2012a5eeb4 (andialbrecht/sqlparse)

Fix landed in andialbrecht/sqlparse commit ef2012a5eeb4 — awaiting tagged release

https://github.com/andialbrecht/sqlparse/commit/ef2012a5eeb491e604dea2b00d516904a3830c87
github Patch Available🟡 PoC Available

Quadratic O(n²) DoS in group_comments · Advisory · andialbrecht/sqlparse · GitHub

https://github.com/andialbrecht/sqlparse/security/advisories/GHSA-f2ff-p2ww-7p4p

Patch Availability(13)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
sqlparse0.4.2-1 ... 0.5.5-2 (11 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
sqlparse0.5.3-1, 0.5.4-1, 0.5.5-1, 0.5.5-2
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
sqlparse0.5.3-1, 0.5.4-1, 0.5.5-1, 0.5.5-2
  • every version on: no fix on record
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
sqlparse0.1.0 ... 0.5.5 (38 versions)
  • every version up to 0.6.0: fixed in 0.6.0
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(3)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 19× in last 7d / 97× 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.

Showing the most recent 100 of 142 total refreshes for this CVE.

  1. 2026-10-04 23:22 UTCEPSS rescore
  2. 2026-10-04 21:49 UTCVendor advisory
  3. 2026-10-04 05:51 UTCVendor advisory
  4. 2026-10-03 17:48 UTCEG score recompute
  5. 2026-10-03 17:48 UTCVendor advisory
  6. 2026-10-03 14:26 UTCEPSS rescore
  7. 2026-10-02 15:45 UTCVendor advisory
  8. 2026-10-02 01:34 UTCEG score recompute
  9. 2026-10-02 01:34 UTCVendor advisory
  10. 2026-10-01 19:50 UTCEPSS rescore
  11. 2026-10-01 10:07 UTCVendor advisory
  12. 2026-09-30 22:03 UTCEG score recompute
  13. 2026-09-30 22:03 UTCVendor advisory
  14. 2026-09-30 15:03 UTCEPSS rescore
  15. 2026-09-30 10:00 UTCEG score recompute
  16. 2026-09-30 10:00 UTCVendor advisory
  17. 2026-09-28 21:59 UTCEG score recompute
  18. 2026-09-28 21:59 UTCVendor advisory
  19. 2026-09-28 13:52 UTCEPSS rescore
  20. 2026-09-28 09:44 UTCVendor advisory
  21. 2026-09-27 21:40 UTCEG score recompute
  22. 2026-09-27 21:40 UTCVendor advisory
  23. 2026-09-27 13:48 UTCEPSS rescore
  24. 2026-09-27 08:06 UTCEG score recompute
  25. 2026-09-27 08:06 UTCVendor advisory
Show 75 more
  1. 2026-09-26 15:59 UTCEPSS rescore
  2. 2026-09-25 04:18 UTCVendor advisory
  3. 2026-09-24 16:14 UTCEG score recompute
  4. 2026-09-24 16:14 UTCVendor advisory
  5. 2026-09-24 03:00 UTCEG score recompute
  6. 2026-09-24 03:00 UTCVendor advisory
  7. 2026-09-23 17:54 UTCEPSS rescore
  8. 2026-09-23 14:56 UTCVendor advisory
  9. 2026-09-23 02:51 UTCEG score recompute
  10. 2026-09-23 02:51 UTCVendor advisory
  11. 2026-09-22 14:47 UTCVendor advisory
  12. 2026-09-22 02:39 UTCEG score recompute
  13. 2026-09-22 02:39 UTCVendor advisory
  14. 2026-09-21 21:09 UTCEPSS rescore
  15. 2026-09-21 14:32 UTCVendor advisory
  16. 2026-09-21 02:19 UTCEG score recompute
  17. 2026-09-21 02:19 UTCVendor advisory
  18. 2026-09-20 20:16 UTCEPSS rescore
  19. 2026-09-20 14:13 UTCVendor advisory
  20. 2026-09-20 00:53 UTCEG score recompute
  21. 2026-09-20 00:53 UTCVendor advisory
  22. 2026-09-19 12:50 UTCVendor advisory
  23. 2026-09-19 00:46 UTCEG score recompute
  24. 2026-09-19 00:46 UTCVendor advisory
  25. 2026-09-18 19:28 UTCEPSS rescore
  26. 2026-09-18 12:42 UTCVendor advisory
  27. 2026-09-18 00:18 UTCEG score recompute
  28. 2026-09-18 00:18 UTCVendor advisory
  29. 2026-09-17 12:14 UTCVendor advisory
  30. 2026-09-17 00:10 UTCEG score recompute
  31. 2026-09-17 00:10 UTCVendor advisory
  32. 2026-09-16 14:08 UTCEPSS rescore
  33. 2026-09-16 12:06 UTCEG score recompute
  34. 2026-09-16 12:06 UTCVendor advisory
  35. 2026-09-16 05:15 UTCEPSS rescore
  36. 2026-09-16 00:02 UTCVendor advisory
  37. 2026-09-15 11:44 UTCEG score recompute
  38. 2026-09-15 11:44 UTCVendor advisory
  39. 2026-09-15 03:12 UTCEPSS rescore
  40. 2026-09-14 22:28 UTCVendor advisory
  41. 2026-09-14 10:17 UTCVendor advisory
  42. 2026-09-13 22:14 UTCEG score recompute
  43. 2026-09-13 22:14 UTCVendor advisory
  44. 2026-09-13 10:10 UTCVendor advisory
  45. 2026-09-12 22:06 UTCEG score recompute
  46. 2026-09-12 22:06 UTCVendor advisory
  47. 2026-09-12 15:02 UTCEPSS rescore
  48. 2026-09-12 10:02 UTCVendor advisory
  49. 2026-09-11 21:58 UTCEG score recompute
  50. 2026-09-11 21:58 UTCVendor advisory
  51. 2026-09-11 14:53 UTCEPSS rescore
  52. 2026-09-11 09:54 UTCEG score recompute
  53. 2026-09-11 09:54 UTCVendor advisory
  54. 2026-09-10 21:47 UTCVendor advisory
  55. 2026-09-10 09:42 UTCEG score recompute
  56. 2026-09-10 09:42 UTCVendor advisory
  57. 2026-09-10 09:35 UTCEPSS rescore
  58. 2026-09-09 21:28 UTCVendor advisory
  59. 2026-09-09 15:43 UTCVendor advisory
  60. 2026-09-09 03:39 UTCEG score recompute
  61. 2026-09-09 03:39 UTCVendor advisory
  62. 2026-09-08 22:01 UTCEPSS rescore
  63. 2026-09-08 04:15 UTCVendor advisory
  64. 2026-09-07 16:11 UTCEG score recompute
  65. 2026-09-07 16:11 UTCVendor advisory
  66. 2026-09-07 01:08 UTCEG score recompute
  67. 2026-09-07 01:08 UTCVendor advisory
  68. 2026-09-06 13:48 UTCEPSS rescore
  69. 2026-09-06 12:46 UTCVendor advisory
  70. 2026-09-06 00:42 UTCEG score recompute
  71. 2026-09-06 00:42 UTCVendor advisory
  72. 2026-09-05 12:37 UTCVendor advisory
  73. 2026-09-05 00:14 UTCEG score recompute
  74. 2026-09-05 00:14 UTCVendor advisory
  75. 2026-09-04 11:09 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-71491?
CVE-2026-71491 is a high vulnerability published on August 17, 2026. sqlparse is a non-validating SQL parser module for Python. Prior to 0.6.0, groupcomments in sqlparse/engine/grouping.py repeatedly rescans comment-only statements before the MAXGROUPINGTOKENS guard, causing quadratic CPU consumption through sqlparse.parse() and sqlparse.format(sql,…
When was CVE-2026-71491 disclosed?
CVE-2026-71491 was first published on August 17, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-71491 actively exploited?
CVE-2026-71491 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (16th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-71491?
CVE-2026-71491 has a CVSS base score of 8.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-71491?
A fix for CVE-2026-71491 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-71491 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-71491

Explore →

Is Your Infrastructure Affected by CVE-2026-71491?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.