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

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

August 17, 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(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.

  1. 2026-08-21 07:23 UTCEG score recompute
  2. 2026-08-20 22:55 UTCEPSS rescore
  3. 2026-08-19 19:55 UTCEG score recompute
  4. 2026-08-19 17:04 UTCEPSS rescore
  5. 2026-08-18 20:15 UTCEG score recompute
  6. 2026-08-18 13:48 UTCEPSS rescore
  7. 2026-08-17 20:29 UTCEG score recompute
  8. 2026-08-17 19:40 UTCEG score recompute
  9. 2026-08-17 18:26 UTCEG score recompute 8.70
  10. 2026-08-17 18:26 UTCNVD updateCVSS v3 → 8.7 · CVSS v4 → 8.7
  11. 2026-08-17 17:54 UTCEG score recompute

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

Explore the affected products and dependency analysis for 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.