vibeio-http has a DoS vulnerability in HTTP/1.x chunked encoding parser triggered by maliciously crafted chunk lengths
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- Denial of service
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub. Impact type from CWE-770.
Summary
When using the affected versions of the `vibeio-http` crate, an attacker could craft a malicious HTTP/1.x request with a large chunk length (between `usize::MAX - 1` and `usize::MAX` inclusive) and send it, causing the server to crash (integer overflow panic in debug builds, split_to out of bounds panic in release builds). This was fixed in `vibeio-http` 0.3.2 by erroring on the chunk length if it exceeds `usize::MAX - 2` (using `checked_add()` instead of `+` operator), preventing integer overflow.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | vibeio-http (crates.io) | before 0.3.2 | 0.3.2 | Patch available | GHSA-fx4f-mhw4-qm7j |
- vibeio-http (crates.io) Vendor— Affected before 0.3.2 Fixed in 0.3.2 Patch available GHSA-fx4f-mhw4-qm7j
Remediation
- Fix · GHSA-fx4f-mhw4-qm7j vibeio-http (crates.io) Fixed in 0.3.2 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-fx4f-mhw4-qm7j
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences