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%, 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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated 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%CVSS: 8.7Exploit: None knownExposed: 0

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.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 computed
Severity87% × 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

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

Vendor Advisories for CVE-2026-71491(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatdiscovery/discovery-server-rhel9:17882057792026-08-31redhat

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 rangeFixed inDependents
sqlparse0.4.2-1 ... 0.5.5-2 (11 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
sqlparse0.5.3-1, 0.5.4-1, 0.5.5-1, 0.5.5-2——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
sqlparse0.5.3-1, 0.5.4-1, 0.5.5-1, 0.5.5-2——
PyPI(1)
PackageVulnerable rangeFixed inDependents
sqlparse0.1.0 ... 0.5.5 (38 versions)0.6.0—

Weakness Classification(2)

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

Data Freshness Timeline

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

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

Related CVEs(same vendor + same CWE)

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 in the National Vulnerability Database 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% probability of exploitation in the next 30 days, which ranks it in the top 81.5% of all scored CVEs.
What is the CVSS score of CVE-2026-71491?
CVE-2026-71491 has a CVSS v3 base score of 8.7 (NVD).
How do I remediate CVE-2026-71491?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-71491, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs