CVE-2026-59893

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 79% 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
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: Elevated riskExposed: 0

A fix is available — apply it.

sqlparse is a non-validating SQL parser module for Python. Prior to 0.6.0, SQL_REGEX in sqlparse/keywords.py and the per-position loop in sqlparse/lexer.py repeatedly scan unmatched dollar-quoted literal and multiline-comment delimiters, causing quadratic CPU consumption through sqlparse.parse(), sqlparse.format(), and sqlparse.split(). This issue is fixed in version 0.6.0.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
65(Attend)
EG Risk 65/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
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
21%
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, github_commit.
github_commit

commit d1d80602741f (andialbrecht/sqlparse)

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

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

Inefficient Regex Handling of Dollar-Quoted SQL Literals Leads to ReDoS (Denial of Service) · Advisory · andialbrecht/sqlparse · GitHub

https://github.com/andialbrecht/sqlparse/security/advisories/GHSA-prg7-hcfm-mfcr

Vendor Advisories for CVE-2026-59893(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(1)

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

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-59893?
CVE-2026-59893 is a high vulnerability published on August 17, 2026. sqlparse is a non-validating SQL parser module for Python. Prior to 0.6.0, SQL_REGEX in sqlparse/keywords.py and the per-position loop in sqlparse/lexer.py repeatedly scan unmatched dollar-quoted literal and multiline-comment delimiters, causing quadratic CPU consumption through sqlparse.parse(),…
When was CVE-2026-59893 disclosed?
CVE-2026-59893 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-59893 actively exploited?
CVE-2026-59893 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 79.4% of all scored CVEs.
What is the CVSS score of CVE-2026-59893?
CVE-2026-59893 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-59893?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-59893, 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-59893

Explore →

Is Your Infrastructure Affected by CVE-2026-59893?

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

Start Free Scan →Browse All CVEs