# CVE-2026-88829: Busybox: busybox: http request smuggling via pipelined requests in httpd reverse proxy

> Attackers can bypass proxy path restrictions via pipelined requests to access arbitrary backend paths in BusyBox httpd reverse proxy configurations.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** AZL-109779, BELL-CVE-2026-88829, DEBIAN-CVE-2026-88829, GHSA-89f7-8rmh-f5q2, UBUNTU-CVE-2026-88829

## What is CVE-2026-88829?

CVE-2026-88829 is a high-severity vulnerability in Red Hat Hardened Images, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A flaw was found in BusyBox httpd's reverse proxy feature. When the proxy is configured to forward requests matching a URL prefix to a backend server, only the first HTTP request on a TCP connection has its path rewritten. An attacker can send a pipelined second request that is relayed verbatim to the backend, bypassing the configured path restrictions. This allows accessing arbitrary paths on the backend server that were not intended to be exposed through the proxy.

Weakness: CWE-444 (Inconsistent Interpretation of HTTP Requests)

## Which versions are affected by CVE-2026-88829?


## How do I fix CVE-2026-88829?

No fix has been published for CVE-2026-88829 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-88829 being exploited?

There is no known exploitation of CVE-2026-88829 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-88829 and fix it if it is affected.

What it is: CVE-2026-88829 is a high-severity vulnerability in Red Hat Hardened Images, published on 14 Oct 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 CVE-2026-88829 in the wild and no public exploit code.

Affected product: Red Hat Hardened Images. No package-level version data is available, so check the vendor advisory linked from the reference page.

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/CVE-2026-88829/ (Markdown: https://insights.sbomify.com/CVE-2026-88829/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-88829
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-88829
- OSV: https://osv.dev/vulnerability/CVE-2026-88829

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-88829/
Summaries are generated and may contain mistakes; the official description above is the record.