{"id":"CVE-2026-32145","aliases":["EEF-CVE-2026-32145","EUVD-2026-18186","GHSA-8645-p2v4-73r2"],"status":"published","title":"Multipart form body parser bypasses body size limits in wisp","description":"Allocation of Resources Without Limits or Throttling vulnerability in gleam-wisp wisp allows a denial of service via multipart form body parsing.\n\nThe 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.\n\nAn unauthenticated attacker can exhaust server memory or disk by sending arbitrarily large multipart form submissions in a single HTTP request.\n\nThis issue affects wisp: from 0.2.0 before 2.2.2.","severity":{"version":"4.0","score":8.7,"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","level":"high","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-10","score":0.00633,"percentile":0.50675,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-770"],"published":"2026-04-02T10:30:47Z","modified":"2026-10-28T02:30:28Z","fixes":[{"ecosystem":"Hex","package":"wisp","fixed_in":["2.2.2"],"sources":["ghsa","osv"]}],"affected":[{"source":"ghsa","ecosystem":"Hex","package":"wisp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.2.2"}]}]},{"source":"osv","ecosystem":"Hex","package":"wisp","ranges":[{"type":"SEMVER","events":[{"introduced":"0.2.0"},{"fixed":"2.2.2"}]}],"versions":["0.10.0","0.11.0","0.12.0","0.13.0","0.14.0","0.15.0","0.16.0","0.2.0","0.3.0","0.4.0","0.5.0","0.6.0","0.7.0","0.8.0","0.9.0","1.0.0","1.1.0","1.2.0","1.3.0","1.4.0","1.5.1","1.5.2","1.5.3","1.6.0","1.7.0","1.8.0","2.0.0","2.0.0-rc1","2.0.1","2.1.0","2.1.1","2.2.0","2.2.1"]},{"source":"osv","ecosystem":"Hex","package":"wisp","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2.2.2"}]}],"versions":["0.1.0","0.10.0","0.11.0","0.12.0","0.13.0","0.14.0","0.15.0","0.16.0","0.2.0","0.3.0","0.4.0","0.5.0","0.6.0","0.7.0","0.8.0","0.9.0","1.0.0","1.1.0","1.2.0","1.3.0","1.4.0","1.5.1","1.5.2","1.5.3","1.6.0","1.7.0","1.8.0","2.0.0","2.0.0-rc1","2.0.1","2.1.0","2.1.1","2.2.0","2.2.1"]}],"products":[{"vendor":"gleam-wisp","product":"wisp"}],"references":[{"url":"https://github.com/gleam-wisp/wisp/security/advisories/GHSA-8645-p2v4-73r2","tags":["vendor-advisory","related","Vendor Advisory","advisory","web"]},{"url":"https://cna.erlef.org/cves/CVE-2026-32145.html","tags":["related","Patch","Third Party Advisory","web"]},{"url":"https://osv.dev/vulnerability/EEF-CVE-2026-32145","tags":["related","Third Party Advisory","web"]},{"url":"https://github.com/gleam-wisp/wisp/commit/7a978748e12ab29db232c222254465890e1a4a90","tags":["patch","Patch","fix","web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-32145","tags":["advisory"]},{"url":"https://github.com/advisories/GHSA-8645-p2v4-73r2"},{"url":"https://github.com","tags":["web"]},{"url":"https://repo.hex.pm","tags":["web"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/32xxx/CVE-2026-32145.json","tags":["advisory"]},{"url":"https://github.com/gleam-wisp/wisp","tags":["package"]},{"url":"https://github.com/gleam-wisp/wisp.git","tags":["package"]},{"url":"https://hex.pm/packages/wisp","tags":["package"]}],"sources":{"cve":[{"id":"CVE-2026-32145","title":"Multipart form body parser bypasses body size limits in wisp","description":"Allocation of Resources Without Limits or Throttling vulnerability in gleam-wisp wisp allows a denial of service via multipart form body parsing.\n\nThe 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.\n\nAn unauthenticated attacker can exhaust server memory or disk by sending arbitrarily large multipart form submissions in a single HTTP request.\n\nThis issue affects wisp: from 0.2.0 before 2.2.2.","status":"published","published":"2026-04-02T10:30:47.485Z","modified":"2026-04-07T04:07:10.339Z","cvss":[{"version":"4.0","score":8.7,"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","level":"high","assessor":"cna"}],"cwes":["CWE-770"],"updated_at":"2026-11-02T14:19:57.47301Z"}],"euvd":[{"id":"EUVD-2026-18186","description":"Allocation of Resources Without Limits or Throttling vulnerability in gleam-wisp wisp allows a denial of service via multipart form body parsing.\n\nThe 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.\n\nAn unauthenticated attacker can exhaust server memory or disk by sending arbitrarily large multipart form submissions in a single HTTP request.\n\nThis issue affects wisp: from 0.2.0 before 2.2.2.","status":"published","published":"2026-04-02T10:30:47Z","modified":"2026-04-07T04:07:10Z","cvss":[{"version":"4.0","score":8.7,"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","level":"high"}],"updated_at":"2026-11-02T19:25:15.380284Z"}],"ghsa":[{"id":"GHSA-8645-p2v4-73r2","title":"wisp has Allocation of Resources Without Limits or Throttling","description":"### Summary\nA 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.\n\n### Details\nThe issue is in the multipart parsing logic, specifically in `multipart_body` and `multipart_headers`.\n\nWhen parsing multipart data, the implementation distinguishes between:\n- chunks where a boundary is found\n- chunks where more data is required\n\nIn the normal case (boundary found), the parser correctly accounts for consumed bytes by calling `decrement_quota`.\n\nHowever, 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.\n\nThe same pattern exists in `multipart_headers`, where `MoreRequiredForHeaders` also recurses without decrementing the quota.\n\nAs 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`.\n\n### Impact\nThis is a denial of service vulnerability caused by uncontrolled resource consumption.\n\nAny application using `require_form` or `require_multipart_form` on user-controlled input is affected. An unauthenticated attacker can send large multipart requests that bypass configured limits and cause:\n\n- memory exhaustion (for form fields accumulated in memory)\n- disk exhaustion (for file uploads written to temporary storage)\n\nIn both cases, the application may become unavailable or be terminated by the operating system.\n\n### Workaround\nDeploy a reverse proxy (such as nginx or HAProxy) in front of the application and enforce request body size limits there. This ensures large multipart requests are rejected before they reach the vulnerable parser.\n\n### Resources\n- Introducing commit: https://github.com/gleam-wisp/wisp/commit/d8e722e22ccb42bda9d0b6248658d37ab4e9b376\n- Fix commit: https://github.com/gleam-wisp/wisp/commit/7a978748e12ab29db232c222254465890e1a4a90","status":"published","published":"2026-04-03T03:40:30Z","modified":"2026-04-06T23:17:48Z","cvss":[{"version":"4.0","score":8.7,"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","level":"high"}],"cwes":["CWE-770"],"updated_at":"2026-11-02T14:39:50.076383Z"}],"nvd":[{"id":"CVE-2026-32145","description":"Allocation of Resources Without Limits or Throttling vulnerability in gleam-wisp wisp allows a denial of service via multipart form body parsing.\n\nThe 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.\n\nAn unauthenticated attacker can exhaust server memory or disk by sending arbitrarily large multipart form submissions in a single HTTP request.\n\nThis issue affects wisp: from 0.2.0 before 2.2.2.","status":"published","published":"2026-04-02T11:16:21.87Z","modified":"2026-10-26T22:10:00.163Z","cvss":[{"version":"4.0","score":8.7,"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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","level":"high","assessor":"secondary"},{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high","assessor":"primary"}],"cwes":["CWE-770"],"updated_at":"2026-11-02T14:12:12.73929Z"}],"osv":[{"id":"CVE-2026-32145","title":"Multipart form body parser bypasses body size limits in wisp","description":"Allocation of Resources Without Limits or Throttling vulnerability in gleam-wisp wisp allows a denial of service via multipart form body parsing.\n\nThe 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.\n\nAn unauthenticated attacker can exhaust server memory or disk by sending arbitrarily large multipart form submissions in a single HTTP request.\n\nThis issue affects wisp: from 0.2.0 before 2.2.2.","status":"published","published":"2026-04-02T10:30:47.485Z","modified":"2026-10-28T02:30:28.546775276Z","cvss":[{"version":"4.0","score":8.7,"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","level":"high"}],"cwes":["CWE-770"],"updated_at":"2026-11-02T15:45:01.218144Z"},{"id":"EEF-CVE-2026-32145","title":"Multipart form body parser bypasses body size limits in wisp","description":"## Summary\n\nAllocation of Resources Without Limits or Throttling vulnerability in gleam-wisp wisp allows a denial of service via multipart form body parsing.\n\nThe 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.\n\nAn unauthenticated attacker can exhaust server memory or disk by sending arbitrarily large multipart form submissions in a single HTTP request.\n\nThis issue affects wisp: from 0.2.0 before 2.2.2.\n\n## Workarounds\n\nDeploy a reverse proxy (such as nginx or HAProxy) in front of the wisp application and configure it to enforce request body size limits.","status":"published","published":"2026-04-02T10:30:47.485Z","modified":"2026-09-08T03:30:11.640106439Z","cvss":[{"version":"4.0","score":8.7,"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","level":"high"}],"cwes":["CWE-770"],"updated_at":"2026-11-02T15:46:33.047032Z"},{"id":"GHSA-8645-p2v4-73r2","title":"wisp has Allocation of Resources Without Limits or Throttling","description":"### Summary\nA 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.\n\n### Details\nThe issue is in the multipart parsing logic, specifically in `multipart_body` and `multipart_headers`.\n\nWhen parsing multipart data, the implementation distinguishes between:\n- chunks where a boundary is found\n- chunks where more data is required\n\nIn the normal case (boundary found), the parser correctly accounts for consumed bytes by calling `decrement_quota`.\n\nHowever, 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.\n\nThe same pattern exists in `multipart_headers`, where `MoreRequiredForHeaders` also recurses without decrementing the quota.\n\nAs 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`.\n\n### Impact\nThis is a denial of service vulnerability caused by uncontrolled resource consumption.\n\nAny application using `require_form` or `require_multipart_form` on user-controlled input is affected. An unauthenticated attacker can send large multipart requests that bypass configured limits and cause:\n\n- memory exhaustion (for form fields accumulated in memory)\n- disk exhaustion (for file uploads written to temporary storage)\n\nIn both cases, the application may become unavailable or be terminated by the operating system.\n\n### Workaround\nDeploy a reverse proxy (such as nginx or HAProxy) in front of the application and enforce request body size limits there. This ensures large multipart requests are rejected before they reach the vulnerable parser.\n\n### Resources\n- Introducing commit: https://github.com/gleam-wisp/wisp/commit/d8e722e22ccb42bda9d0b6248658d37ab4e9b376\n- Fix commit: https://github.com/gleam-wisp/wisp/commit/7a978748e12ab29db232c222254465890e1a4a90","status":"published","published":"2026-04-03T03:40:30Z","modified":"2026-04-06T23:32:52.065422Z","cvss":[{"version":"4.0","score":8.7,"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","level":"high"}],"cwes":["CWE-770"],"updated_at":"2026-11-02T15:46:41.732368Z"}]}}