Skip to main content
CVE-2026-53539VulnerabilityPublished Updated

semgrep · python-multipart: Quadratic-time querystring parsing with semicolon separators causes CPU denial of service

Affects semgrepSource GCVE Database

0
Compare
Authoritative record:CVE-2026-53539· High 7.5

Not known to be exploited · CVSS 7.5 High : upgrade to 1.165.0 soon.

Data as of 19 Nov 2026, 19:38 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 1.165.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade semgrep to 1.165.0.

Affected software

ProductAffectedFixed in
Homebrewsemgreppkg:brew/semgrepOther threatsAffected
  • >=1.137.0 <1.165.0
Fixed in
  • 1.165.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade python-multipart to version 1.165.0 or later. This version changes the parser to treat only '&' as a field separator, eliminating the quadratic-time parsing issue and ensuring linear-time parsing. No other mitigation is required.

Description

A vulnerability in python-multipart's QuerystringParser causes quadratic-time parsing when processing application/x-www-form-urlencoded bodies with semicolon separators and no ampersands. This leads to excessive CPU consumption, enabling denial of service by exhausting worker processes. The issue is fixed in version 1.165.0 by restricting separators to ampersands only, making parsing linear in time.

References

Community reviews

Loading reviews…