CVE-2026-88829
validatedZero produced an exploit or a check.GHSA-89f7-8rmh-f5q2 ↗EUVD-2026-100952 ↗
description
BusyBox httpd reverse-proxy deployments that forward a URL prefix to a backend are affected. An unauthenticated remote attacker may reach backend paths outside the intended proxy prefix by abusing request handling on a reused connection. The issue requires the reverse proxy feature and prefix-based backend forwarding to be configured.
mitigation
Disable BusyBox httpd reverse-proxy forwarding or place a proxy that enforces per-request path validation in front of the backend. Restrict backend access so it accepts requests only from trusted proxy infrastructure.
outcome
Check only, differential: the check fires on the vulnerable build and is silent on the patched one.
source signals
Public signals that triggered or updated the pipeline. These are inputs for the deltas above.
- 2026-10-14 10:00Zcve_org: trigger signal, started the run
this entry in the feed
GET /api/v1/feed/CVE-2026-88829
{ "etk_id": "ETK-2026-1916", "cve_id": "CVE-2026-88829", "display_id": "CVE-2026-88829", "ghsa_id": "GHSA-89f7-8rmh-f5q2", "euvd_id": "EUVD-2026-100952", "status": "published", "anchor_state": "anchored", "title": "Path restriction bypass in BusyBox httpd reverse proxy", "summary": "BusyBox httpd reverse-proxy deployments that forward a URL prefix to a backend are affected. An unauthenticated remote attacker may reach backend paths outside the intended proxy prefix by abusing request handling on a reused connection. The issue requires the reverse proxy feature and prefix-based backend forwarding to be configured.", "mitigation": "Disable BusyBox httpd reverse-proxy forwarding or place a proxy that enforces per-request path validation in front of the backend. Restrict backend access so it accepts requests only from trusted proxy infrastructure.", "vendor": "Red Hat", "product": "Red Hat Hardened Images", "affected": [ { "affected_notes": [], "affected_ranges": [], "ecosystem": null, "fixed_versions": [], "package_name": "busybox", "purl": null } ], "cwes": [ 444 ], "cvss_score": 7.2, "cvss_src": "cna_vendor", "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N", "epss_score": 0.0032, "epss_percentile": 0.2332, "epss_asof": "2026-10-21", "automation": "deterministic", "check": true, "check_confidence_basis": "differential", "exploit": false, "pipeline_minutes": 28.315459466666667, "t0_at": "2026-10-14T10:00:42.946000+00:00", "signals": { "check": { "at": "2026-10-18T00:04:06.354889+00:00", "days": 3.5856876028819444, "is_lower_bound": false, "measured_at": "2026-10-14T10:00:42.946000+00:00", "url": null }, "trigger_signal": { "at": "2026-10-14T10:00:42.946000+00:00", "days": 0, "is_lower_bound": false, "measured_at": "2026-10-14T10:00:42.946000+00:00", "url": "https://www.cve.org/CVERecord?id=CVE-2026-88829" } } }
published 2026-10-17 23:35Z
last change 2026-10-21 22:34Z
Need the technical details behind an entry?
Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.