Skip to content
CVE-2026-88829: BusyBox httpd Reverse Proxy Vulnerability

CVE-2026-88829: BusyBox httpd Reverse Proxy Vulnerability

First seen 15 Oct 2026, 01:38 UTC • •

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •October 15, 2026 at 01:39 UTC
  • •CVE-2026-88829 allows unauthorized backend access via pipelined requests.
  • •Red Hat's Fedora is affected; RHEL does not include BusyBox by default.
  • •Immediate action is recommended to enhance access controls and proxy configurations.

A flaw in BusyBox httpd's reverse proxy feature allows attackers to bypass path restrictions by sending pipelined requests. This vulnerability, identified as CVE-2026-88829, affects systems using path-based proxy rules, particularly in embedded or containerized deployments. The flaw enables unauthorized access to backend server paths that should remain restricted. Red Hat has noted that while Fedora is affected, RHEL does not ship BusyBox as a standard package. The CVSS score for this vulnerability is 7.2, indicating a high severity. No proof-of-concept or has been confirmed. Administrators are advised to implement additional access controls and consider using a full reverse proxy. The flaw was published on October 14, 2026, and is currently under review for impact analysis.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Updated just now How this analysis works

Timeline

2026-10-14
CVE-2026-88829 published
The vulnerability in BusyBox httpd's reverse proxy feature was disclosed with a CVSS score of 7.2.
access.redhat.com

More articles in this cluster (2)

Following this threat?

Track CVE-2026-88829 in your own feed — you're alerted when they show up in new reporting, leak sites or exploitation.

Free account · no card needed

Common questions

Which systems are affected by CVE-2026-88829?
The vulnerability primarily affects Fedora systems using BusyBox with reverse proxy rules enabled.
What should I do to mitigate this vulnerability?
Remove unnecessary proxy rules, enforce access controls at the backend, and consider using a full-featured reverse proxy.
Is there any active exploitation of this vulnerability?
No, there is currently no confirmed active exploitation or proof-of-concept code available.