CVE-2026-88829

Busybox: busybox: http request smuggling via pipelined requests in httpd reverse proxy

  • High 7.2

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.

Key facts

Published
14 Oct 2026
Last changed
11 Nov 2026
Assigned by
redhat
EPSS
0.261% likely to be exploited in the next 30 days, higher than 17.987% of CVEs (scores for 18 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: yes; Technical impact: partial

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 7.2CVSS 3.1, Highfrom the CNA (redhat)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

What to do

  • Do not use BusyBox httpd P: rules as the sole path-based access control in front of sensitive backends. Remove P: lines if proxying is not required, or place a full reverse proxy (for example nginx or HAProxy) in front of the backend. Recompile with FEATURE_HTTPD_PROXY disabled if the applet is not needed.CNA workaround statement

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
Red HatRed Hat Hardened Images
  • Default status: affected

Timeline

  1. 7 Sep 2026 Reported to Red Hat.
  2. 14 Oct 2026 Made public.
  3. 14 Oct 2026 Published

Weakness

References