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% (24th 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 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.3%CVSS: 8.7Exploit: Elevated riskExposed services: Not assessed

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.7HIGHmedium confidence
EG Risk
70
EG Risk 70/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%
Exploitation40% × 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
24th
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 public PoC (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 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(20)

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

Patch Availability(18)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntusqlformat (0.4.2-1ubuntu0.22.04.3) @ jammy2026-10-05ubuntu
redhatpython3.12-sqlparse-0:0.6.0-1.el9pc2026-10-01redhat
redhatsatellite/iop-advisor-backend-rhel9:17896664992026-10-01redhat
redhatsatellite/iop-advisor-backend-rhel9:17896664982026-10-01redhat
redhatpython-sqlparse-0:0.6.0-1.el9pc2026-10-01redhat
redhatopenshift4/ose-ironic-rhel9:17899376342026-10-01redhat
redhatpython3.12-sqlparse-0:0.6.0-1.el9ap2026-09-23redhat
redhatansible-automation-platform-27/hub-rhel9:17895726322026-09-23redhat
redhatansible-automation-platform-25/lightspeed-rhel8:17896858372026-09-23redhat
redhatansible-automation-platform-tech-preview/metrics-service-rhel9:17896545582026-09-23redhat
redhatrhoai/odh-training-cuda128-torch29-py312-rhel9:17895298512026-09-21redhat
redhatopenshift4/ose-ironic-rhel9:17885755552026-09-17redhat
redhatopenshift4/ose-ironic-rhel9:17888970412026-09-16redhat
redhatopenshift4/ose-ironic-rhel9:17889471392026-09-15redhat
redhatopenshift4/ose-ironic-rhel9:17889282452026-09-15redhat
redhatopenshift4/ose-ironic-rhel9:17889619092026-09-15redhat
redhatansible-automation-platform-27/metrics-service-rhel9:17889170582026-09-14redhat
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 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 25× in last 7d / 101× 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 146 total refreshes for this CVE.

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

Related CVEs(same product + 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 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.3% probability of exploitation in the next 30 days (24th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-54284?
CVE-2026-54284 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-54284?
A fix for CVE-2026-54284 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-54284 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-54284

Explore →

Is Your Infrastructure Affected by CVE-2026-54284?

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

Book a Demo →Browse All CVEs