CVE-2026-32145: Wisp Remote Code Execution Vulnerability
HIGHCVE-2026-32145 is a HIGH remote code execution vulnerability (CWE-770: Allocation of Resources Without Limits or Throttling) affecting Wisp libraries in the Hex ecosystem. The issue involves wisp has allocation of resources without limits or throttling. Remediation is available by upgrading affected packages to version 2.2.2.
CVE-2026-32145 at a Glance
How to Fix CVE-2026-32145
To remediate this vulnerability, upgrade all affected Wisp dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade wisp to 2.2.2
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for wisp
How to Check if You Are Affected
To determine whether your application is affected by CVE-2026-32145, inspect your project dependencies for Wisp:
inspect dependencies for wisp
Analyze the terminal output to locate any version of Wisp in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.2.2), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-770: Allocation of Resources Without Limits or Throttling, where the product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated. In Wisp, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-32145 Affected Wisp Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
wisp
|
Hex |
< 2.2.2
|
2.2.2
|
References
Frequently Asked Questions
What is CVE-2026-32145?
Which Wisp versions are affected?
What version fixes CVE-2026-32145?
Is wisp affected?
What CWE is associated with CVE-2026-32145?
How can I check Hex dependencies for CVE-2026-32145?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-8645-p2v4-73r2",
"modified" : "2026-04-06T23:17:44Z",
"published" : "2026-04-03T03:40:30Z",
"aliases" : [ "CVE-2026-32145" ],
"summary" : "wisp has Allocation of Resources Without Limits or Throttling",
"details" : "### 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",
"severity" : [ {
"type" : "CVSS_V4",
"score" : "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"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Hex",
"name" : "wisp"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "2.2.2"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/gleam-wisp/wisp/security/advisories/GHSA-8645-p2v4-73r2"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-32145"
}, {
"type" : "WEB",
"url" : "https://github.com/gleam-wisp/wisp/commit/7a978748e12ab29db232c222254465890e1a4a90"
}, {
"type" : "WEB",
"url" : "https://cna.erlef.org/cves/CVE-2026-32145.html"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/gleam-wisp/wisp"
}, {
"type" : "WEB",
"url" : "https://osv.dev/vulnerability/EEF-CVE-2026-32145"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-770" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-04-03T03:40:30Z",
"nvd_published_at" : "2026-04-02T11:16:21Z"
}
}