# GHSA-fx4f-mhw4-qm7j: vibeio-http has a DoS vulnerability in HTTP/1.x chunked encoding parser triggered by maliciously crafted chunk lengths

> An attacker can crash the server by sending a malicious HTTP request with an excessively large chunk length, causing an integer overflow panic.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Jun 2026
- **Also known as:** RUSTSEC-2026-0181

## What is GHSA-fx4f-mhw4-qm7j?

GHSA-fx4f-mhw4-qm7j is a vulnerability in vibeio-http, published on 6 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

## Which versions are affected by GHSA-fx4f-mhw4-qm7j?

3 open source packages ship an affected version, including vibeio-http.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `vibeio-http` | crates.io | All versions | 0.3.2 |
| `vibeio-http` | crates.io | All versions | 0.3.2 |
| `vibeio-http` | crates.io | From 0.0.0-0 | 0.3.2 |

## How do I fix GHSA-fx4f-mhw4-qm7j?

Upgrade vibeio-http to 0.3.2 or later.

## Is GHSA-fx4f-mhw4-qm7j being exploited?

There is no known exploitation of GHSA-fx4f-mhw4-qm7j in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-fx4f-mhw4-qm7j and fix it if it is affected.

What it is: GHSA-fx4f-mhw4-qm7j is a vulnerability in vibeio-http, published on 6 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-fx4f-mhw4-qm7j in the wild and no public exploit code.

Affected packages and fixed versions:
- vibeio-http (crates.io): affected all versions; fixed in 0.3.2
- vibeio-http (crates.io): affected all versions; fixed in 0.3.2
- vibeio-http (crates.io): affected from 0.0.0-0; fixed in 0.3.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-fx4f-mhw4-qm7j/ (Markdown: https://insights.sbomify.com/GHSA-fx4f-mhw4-qm7j/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-fx4f-mhw4-qm7j

---
From sbomify Insights: https://insights.sbomify.com/GHSA-fx4f-mhw4-qm7j/
Summaries are generated and may contain mistakes; the official description above is the record.