CVE-2026-54284

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 weekElevated
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: Elevated riskExposed: 0

A fix is available — apply it.

sqlparse is a non-validating SQL parser module for Python. Prior to 0.6.0, TokenList construction and string conversion in sqlparse/sql.py repeatedly flatten nested token subtrees constructed by group_parenthesis and group_case, causing quadratic CPU consumption through sqlparse.parse(), sqlparse.format(), and sqlparse.split() before depth and token limits terminate processing. This issue is fixed in version 0.6.0.

CVSS v3
8.7
EG Score
8.7(medium)
EG Risk
70(Attend)
EG Risk 70/100SSVC: Attend

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%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
18%
KEV
Not listed

Published

August 17, 2026

Last Modified

September 18, 2026

Advisory Details (2)

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

TokenList.__init__ materializes O(subtree) value per group, causing CPU DoS before depth/token caps trigger · Advisory · andialbrecht/sqlparse · GitHub

https://github.com/andialbrecht/sqlparse/security/advisories/GHSA-pwgv-4x5q-6m9f
github_commit

commit 939b129e24c0 (andialbrecht/sqlparse)

Fix landed in andialbrecht/sqlparse commit 939b129e24c0 — awaiting tagged release

https://github.com/andialbrecht/sqlparse/commit/939b129e24c0ad5d51368b1aa72fffcaca76f06f

Vendor Advisories for CVE-2026-54284(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 25× in last 7d / 84× 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-18 20:21 UTCEG score recompute
  2. 2026-09-18 20:21 UTCVendor advisory
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-18 15:20 UTCVendor advisory
  5. 2026-09-18 03:31 UTCEG score recompute
  6. 2026-09-18 03:31 UTCVendor advisory
  7. 2026-09-17 19:31 UTCEPSS rescore
  8. 2026-09-17 15:42 UTCVendor advisory
  9. 2026-09-17 03:44 UTCVendor advisory
  10. 2026-09-16 15:15 UTCEG score recompute
  11. 2026-09-16 15:15 UTCVendor advisory
  12. 2026-09-16 14:08 UTCEPSS rescore
  13. 2026-09-16 05:15 UTCEPSS rescore
  14. 2026-09-16 01:28 UTCVendor advisory
  15. 2026-09-15 13:39 UTCEG score recompute
  16. 2026-09-15 13:39 UTCVendor advisory
  17. 2026-09-15 01:42 UTCVendor advisory
  18. 2026-09-14 13:53 UTCVendor advisory
  19. 2026-09-14 02:04 UTCEG score recompute
  20. 2026-09-14 02:04 UTCVendor advisory
  21. 2026-09-13 16:47 UTCEPSS rescore
  22. 2026-09-13 14:14 UTCVendor advisory
  23. 2026-09-13 02:25 UTCEG score recompute
  24. 2026-09-13 02:25 UTCVendor advisory
  25. 2026-09-12 14:35 UTCVendor advisory
Show 68 more
  1. 2026-09-12 02:46 UTCVendor advisory
  2. 2026-09-11 14:56 UTCEG score recompute
  3. 2026-09-11 14:56 UTCVendor advisory
  4. 2026-09-11 14:53 UTCEPSS rescore
  5. 2026-09-11 03:07 UTCVendor advisory
  6. 2026-09-10 15:16 UTCEG score recompute
  7. 2026-09-10 15:16 UTCVendor advisory
  8. 2026-09-10 09:35 UTCEPSS rescore
  9. 2026-09-10 03:27 UTCVendor advisory
  10. 2026-09-09 15:38 UTCVendor advisory
  11. 2026-09-09 03:39 UTCEG score recompute
  12. 2026-09-09 03:39 UTCVendor advisory
  13. 2026-09-08 22:01 UTCEPSS rescore
  14. 2026-09-07 22:23 UTCEG score recompute
  15. 2026-09-07 22:23 UTCVendor advisory
  16. 2026-09-07 16:01 UTCEPSS rescore
  17. 2026-09-07 10:33 UTCVendor advisory
  18. 2026-09-06 21:40 UTCEG score recompute
  19. 2026-09-06 21:40 UTCVendor advisory
  20. 2026-09-06 13:47 UTCEPSS rescore
  21. 2026-09-06 09:50 UTCVendor advisory
  22. 2026-09-05 22:01 UTCEG score recompute
  23. 2026-09-05 22:01 UTCVendor advisory
  24. 2026-09-05 10:11 UTCVendor advisory
  25. 2026-09-04 22:21 UTCEG score recompute
  26. 2026-09-04 22:21 UTCVendor advisory
  27. 2026-09-04 10:26 UTCEG score recompute
  28. 2026-09-04 10:26 UTCVendor advisory
  29. 2026-09-04 05:06 UTCEPSS rescore
  30. 2026-09-03 22:37 UTCVendor advisory
  31. 2026-09-03 10:04 UTCVendor advisory
  32. 2026-09-02 22:10 UTCEG score recompute
  33. 2026-09-02 22:10 UTCVendor advisory
  34. 2026-09-02 14:12 UTCEPSS rescore
  35. 2026-09-02 09:35 UTCVendor advisory
  36. 2026-09-01 21:37 UTCEG score recompute
  37. 2026-09-01 21:37 UTCVendor advisory
  38. 2026-09-01 13:54 UTCEPSS rescore
  39. 2026-09-01 09:45 UTCEG score recompute
  40. 2026-09-01 04:40 UTCEPSS rescore
  41. 2026-08-31 06:33 UTCEG score recompute
  42. 2026-08-30 19:17 UTCEPSS rescore
  43. 2026-08-30 06:55 UTCEG score recompute
  44. 2026-08-30 01:22 UTCEPSS rescore
  45. 2026-08-29 05:30 UTCEG score recompute
  46. 2026-08-28 21:41 UTCEPSS rescore
  47. 2026-08-27 19:25 UTCEG score recompute
  48. 2026-08-27 14:25 UTCEPSS rescore
  49. 2026-08-26 18:18 UTCEG score recompute
  50. 2026-08-26 14:46 UTCEPSS rescore
  51. 2026-08-25 17:49 UTCEG score recompute
  52. 2026-08-25 13:49 UTCEPSS rescore
  53. 2026-08-24 18:09 UTCEG score recompute
  54. 2026-08-23 06:40 UTCEG score recompute
  55. 2026-08-23 00:19 UTCEPSS rescore
  56. 2026-08-22 07:01 UTCEG score recompute
  57. 2026-08-21 23:49 UTCEPSS rescore
  58. 2026-08-21 07:23 UTCEG score recompute
  59. 2026-08-20 22:55 UTCEPSS rescore
  60. 2026-08-19 19:55 UTCEG score recompute
  61. 2026-08-19 17:04 UTCEPSS rescore
  62. 2026-08-18 20:15 UTCEG score recompute
  63. 2026-08-18 13:48 UTCEPSS rescore
  64. 2026-08-17 20:29 UTCEG score recompute
  65. 2026-08-17 19:40 UTCEG score recompute
  66. 2026-08-17 18:26 UTCEG score recompute▲ 8.70
  67. 2026-08-17 18:26 UTCNVD updateCVSS v3 → 8.7 · CVSS v4 → 8.7
  68. 2026-08-17 17:54 UTCEG score recompute

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-54284?
CVE-2026-54284 is a high vulnerability published on August 17, 2026. sqlparse is a non-validating SQL parser module for Python. Prior to 0.6.0, TokenList construction and string conversion in sqlparse/sql.py repeatedly flatten nested token subtrees constructed by groupparenthesis and groupcase, causing quadratic CPU consumption through sqlparse.parse(),…
When was CVE-2026-54284 disclosed?
CVE-2026-54284 was first published in the National Vulnerability Database on August 17, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54284 actively exploited?
CVE-2026-54284 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-54284?
CVE-2026-54284 has a CVSS v3 base score of 8.7 (NVD).
How do I remediate CVE-2026-54284?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54284, 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-54284

Explore →

Is Your Infrastructure Affected by CVE-2026-54284?

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

Start Free Scan →Browse All CVEs