Most recent entries from all

EUVD-2026-280580

fkie_cve-2026-32145

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.

GHSA-8645-p2v4-73r2 — wisp has Allocation of Resources Without Limits or Throttling

Affected: Hex: wisp

### Summary A multipart form parsing bug allows any unauthenticated user to bypass configured request size limits and trigger a denial of service by exhausting server memory or disk.

### Details The issue is in the multipart parsing logic, specifically in `multipart_body` and `multipart_headers`.

When parsing multipart data, the implementation distinguishes between: - chunks where a boundary is found - chunks where more data is required

In the normal case (boundary found), the parser correctly accounts for consumed bytes by calling `decrement_quota`.

However, in the `MoreRequiredForBody` branch, the parser appends incoming data to the output but recurses without decrementing the quota. This means that any chunk that does not contain the multipart boundary is effectively “free” from a quota perspective. Only the final chunk, the one containing the boundary, is counted.

The same pattern exists in `multipart_headers`, where `MoreRequiredForHeaders` also recurses without decrementing the quota.

As a result, an attacker can send arbitrarily large multipart bodies split across many chunks that avoid the boundary. The parser will accumulate the data (in memory for form fields, on disk for file uploads) without enforcing `max_body_size` or `max_files_size`.

### Impact This is a denial of service vulnerability caused by uncontrolled resource consumption.

Any application using `require_form` or `require_multipart_form` on user-controlled input is affected. An unauthenticated a…