CVE-2026-53539

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.5%, top 61% 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
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.5%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Python-Multipart is a streaming multipart parser for Python. Prior to 0.0.30, when parsing application/x-www-form-urlencoded bodies, QuerystringParser located the field separator with a two step lookup: it first scanned the entire remaining buffer for &, and only when no & existed anywhere ahead did it fall back to scanning for ;. For a body that uses ; as the separator and contains no &, every field iteration performed a full failed & scan over the entire remaining buffer before locating the nearby ;. With N semicolon separated fields in a chunk of size B, this yields O(B^2) byte comparisons per chunk. An attacker can submit a small crafted body of the form a;a;a;... and cause the parser to spend seconds of CPU per request. A handful of concurrent requests can exhaust worker processes. This vulnerability is fixed in 0.0.30.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100

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%
Exploitation0% × 40%
Automatability100% × 15%
EPSS PROB
0.5%
EPSS %ILE
37th
KEV
Not listed

Published

June 15, 2026

Last Modified

June 26, 2026

Advisory Details (1)

Auto-updated Jun 22, 2026
Patch available. Sources: github.
githubMentions a patch (unverified)

Quadratic-time querystring parsing with semicolon separators causes CPU denial of service · Advisory · Kludex/python-multipart · GitHub

https://github.com/Kludex/python-multipart/security/advisories/GHSA-5rvq-cxj2-64vf

Vendor Advisories for CVE-2026-53539(1)

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 / EcosystemFix (by version range) / PatchReleasedSource
redhatjaeger-main-2.19.0-1.hum12026-06-10redhat

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

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
python-multipart0.0.17-1 ... 0.0.9-1 (14 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
python-multipart0.0.17-1 ... 0.0.9-1 (14 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
python-multipart0.0.20-1 ... 0.0.32-1 (6 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
python-multipart0.0.20-1, 0.0.20-1.1, 0.0.20-1.1~deb13u1, 0.0.22-1, 0.0.26-1
  • every version up to 0.0.32-1: fixed in 0.0.32-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
python-multipart0.0.1 ... 0.0.9 (29 versions)
  • every version up to 0.0.30: fixed in 0.0.30
—

Weakness Classification(2)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 6× in last 7d / 23× 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 141 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-53539?
CVE-2026-53539 is a high vulnerability published on June 15, 2026. Python-Multipart is a streaming multipart parser for Python. Prior to 0.0.30, when parsing application/x-www-form-urlencoded bodies, QuerystringParser located the field separator with a two step lookup: it first scanned the entire remaining buffer for &, and only when no & existed anywhere ahead…
When was CVE-2026-53539 disclosed?
CVE-2026-53539 was first published on June 15, 2026, with the most recent update on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53539 actively exploited?
CVE-2026-53539 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (37th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-53539?
CVE-2026-53539 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-53539?
A fix for CVE-2026-53539 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-53539 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-53539

Explore →

Is Your Infrastructure Affected by CVE-2026-53539?

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