CVE-2026-32145 | gleam-wisp up to 2.2.1 multipart_body allocation of resources

VDB-354849 · CVE-2026-32145 · GCVE-0-2026-32145 GLEAM-WISP UP TO 2.2.1 MULTIPART_BODY ALLOCATION OF RESOURCES HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 5.1 $0-$5k 1.01+ Summaryinfo A vulnerability was found in gleam-wisp wisp up to 2.2.1. It has been classified as problematic. Affected by this vulnerability is the function multipart_body. Performing a manipulation results in allocation of resources. This vulnerability is cataloged as CVE-2026-32145. It is possible to initiate the attack remotely. There is no exploit available. Upgrading the affected component is recommended. Detailsinfo A vulnerability was found in gleam-wisp wisp up to 2.2.1. It has been classified as problematic. This affects the function multipart_body. The manipulation with an unknown input leads to a allocation of resources vulnerability. CWE is classifying the issue as CWE-770. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor. This is going to have an impact on availability. The summary by CVE is: Allocation of Resources Without Limits or Throttling vulnerability in gleam-wisp wisp allows a denial of service via multipart form body parsing. The multipart_body function bypasses configured max_body_size and max_files_size limits. When a multipart boundary is not present in a chunk, the parser takes the MoreRequiredForBody path, which appends the chunk to the output but passes the quota unchanged to the recursive call. Only the final chunk containing the boundary is counted via decrement_quota. The same pattern exists in multipart_headers, where MoreRequiredForHeaders recurses without calling decrement_body_quota. An unauthenticated attacker can exhaust server memory or disk by sending arbitrarily large multipart form submissions in a single HTTP request. This issue affects wisp: from 0.2.0 before 2.2.2. The weakness was shared by John Downey. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-32145 since 03/10/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1499 for this issue. Upgrading to version 2.2.2 eliminates this vulnerability. Productinfo Vendor gleam-wisp Name wisp Version 2.2.0 2.2.1 Website Product: https://github.com/gleam-wisp/wisp/ CPE 2.3info 🔒 🔒 CPE 2.2info 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA CVSS-B Score: 🔒 CNA CVSS-BT Score: 🔒 CNA Vector: 🔒 CVSSv3info VulDB Meta Base Score: 5.3 VulDB Meta Temp Score: 5.1 VulDB Base Score: 5.3 VulDB Temp Score: 5.1 VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Allocation of resources CWE: CWE-770 / CWE-400 / CWE-404 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Yes Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: wisp 2.2.2 Timelineinfo 03/10/2026 CVE reserved 04/02/2026 +22 days Advisory disclosed 04/02/2026 +0 days VulDB entry created 04/02/2026 +0 days VulDB entry last update Sourcesinfo Product: github.com Advisory: github.com Researcher: John Downey Status: Confirmed CVE: CVE-2026-32145 (🔒) GCVE (CVE): GCVE-0-2026-32145 GCVE (VulDB): GCVE-100-354849 Entryinfo Created: 04/02/2026 12:59 Changes: 04/02/2026 12:59 (67) Complete: 🔍 Cache ID: 99:28D:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸