CVE-2026-84305

MEDIUMPre-NVD 5.15.1—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 97% 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
Elevated
5.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.1Exploit: 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, sqlparse.format(sql, reindent=True) and sqlformat --reindent route attacker-controlled parenthesized tuple lists through ReindentFilter._get_offset() in sqlparse/filters/reindent.py, where _flatten_up_to_token() repeatedly rebuilds and joins the statement prefix. Thousands of offset calculations walk an expanding token tree, producing quadratic CPU consumption for inputs that remain below MAX_GROUPING_TOKENS and causing request delays, reduced throughput, or worker starvation. This issue is fixed in version 0.6.0.

CVSS v3
5.1
EG Score
5.1(medium)
EG Risk
39(Track)
EG Risk 39/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
Severity51% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

September 1, 2026

Last Modified

September 9, 2026

Advisory Details (2)

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

commit a51df6d9e2d3 (andialbrecht/sqlparse)

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

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

Reindentation of tuple lists causes near-cap quadratic CPU consumption · Advisory · andialbrecht/sqlparse · GitHub

https://github.com/andialbrecht/sqlparse/security/advisories/GHSA-cfqr-cjx5-5jcm

Vendor Advisories for CVE-2026-84305(1)

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

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(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 30× 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 19:28 UTCEPSS rescore
  2. 2026-09-18 16:41 UTCEG score recompute
  3. 2026-09-17 19:32 UTCEPSS rescore
  4. 2026-09-17 14:18 UTCEG score recompute
  5. 2026-09-16 14:09 UTCEPSS rescore
  6. 2026-09-16 11:44 UTCEG score recompute
  7. 2026-09-16 05:15 UTCEPSS rescore
  8. 2026-09-15 09:22 UTCEG score recompute
  9. 2026-09-15 03:12 UTCEPSS rescore
  10. 2026-09-15 03:12 UTCEPSS rescore
  11. 2026-09-14 07:00 UTCEG score recompute
  12. 2026-09-12 02:16 UTCEG score recompute
  13. 2026-09-11 14:53 UTCEPSS rescore
  14. 2026-09-11 14:53 UTCEPSS rescore
  15. 2026-09-10 23:54 UTCEG score recompute
  16. 2026-09-09 13:44 UTCEG score recompute
  17. 2026-09-08 22:01 UTCEPSS rescore
  18. 2026-09-08 11:00 UTCEG score recompute
  19. 2026-09-07 08:12 UTCEG score recompute
  20. 2026-09-06 13:48 UTCEPSS rescore
  21. 2026-09-06 05:49 UTCEG score recompute
  22. 2026-09-05 15:31 UTCEPSS rescore
  23. 2026-09-05 03:28 UTCEG score recompute
  24. 2026-09-04 05:07 UTCEPSS rescore
  25. 2026-09-02 22:43 UTCEG score recompute
Show 5 more
  1. 2026-09-02 14:12 UTCEPSS rescore
  2. 2026-09-01 20:21 UTCEG score recompute
  3. 2026-09-01 19:29 UTCEG score recompute
  4. 2026-09-01 18:39 UTCEG score recompute
  5. 2026-09-01 18:37 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-84305?
CVE-2026-84305 is a medium vulnerability published on September 1, 2026. sqlparse is a non-validating SQL parser module for Python. Prior to 0.6.0, sqlparse.format(sql, reindent=True) and sqlformat --reindent route attacker-controlled parenthesized tuple lists through ReindentFilter.getoffset() in sqlparse/filters/reindent.py, where flattenuptotoken() repeatedly…
When was CVE-2026-84305 disclosed?
CVE-2026-84305 was first published in the National Vulnerability Database on September 1, 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-84305 actively exploited?
CVE-2026-84305 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 97.4% of all scored CVEs.
What is the CVSS score of CVE-2026-84305?
CVE-2026-84305 has a CVSS v3 base score of 5.1 (NVD).
How do I remediate CVE-2026-84305?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-84305, 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-84305

Explore →

Is Your Infrastructure Affected by CVE-2026-84305?

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

Start Free Scan →Browse All CVEs