CVE-2026-32145 PUBLISHED

Multipart form body parser bypasses body size limits in wisp

Assigner: EEF
Reserved: 10.03.2026 Published: 02.04.2026 Updated: 02.04.2026

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.

Metrics

CVSS Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
CVSS Score: 8.7

Product Status

Vendor gleam-wisp
Product wisp
Versions Default: unaffected
  • affected from 0.2.0 to 2.2.2 (excl.)
  • affected from pkg:hex/wisp@0.2.0 to pkg:hex/wisp@2.2.2 (excl.)
Vendor gleam-wisp
Product wisp
Versions Default: unaffected
  • affected from d8e722e22ccb42bda9d0b6248658d37ab4e9b376 to 7a978748e12ab29db232c222254465890e1a4a90 (excl.)
  • affected from pkg:github/gleam-wisp/wisp@d8e722e22ccb42bda9d0b6248658d37ab4e9b376 to pkg:github/gleam-wisp/wisp@7a978748e12ab29db232c222254465890e1a4a90 (excl.)

Workarounds

Deploy a reverse proxy (such as nginx or HAProxy) in front of the wisp application and configure it to enforce request body size limits.

Credits

  • John Downey finder
  • Louis Pilfold remediation developer

References

Problem Types

  • CWE-770 Allocation of Resources Without Limits or Throttling CWE

Impacts

  • CAPEC-130 Excessive Allocation