BusyBox · CWE-288
Source GCVE Database
Not known to be exploited · CVSS 5.3 Medium.
Data as of 11 Nov 2026, 13:27 UTC
Thin evidence
One scorer or none| CNA (redhat) | CVSS 3.1 | 5.3 |
|---|
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 11 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Red Hat Enterprise Linux 6busybox | Affected– | Fixed in– |
| Red Hat Hardened Imagesbusybox | Affected– | Fixed in– |
AI-suggested
To mitigate this vulnerability, apply one or more of the following configuration changes: (1) Use directory-level authentication rules in httpd.conf instead of file-specific rules, as directory rules apply to both base and compressed files; (2) When protecting individual files, configure password rules for both the uncompressed filename and its .gz compressed counterpart; (3) Restrict network access to the BusyBox httpd daemon using local firewall rules if remote access is unnecessary. Note that changes to httpd.conf require restarting or reloading the httpd process, temporarily interrupting active sessions.
Description
A vulnerability in BusyBox's HTTP daemon (httpd) with pre-compressed file support enabled allows authentication checks to be bypassed. The flaw occurs because authentication is checked against the requested URL path rather than the actual pre-compressed file served. An attacker can exploit this by requesting an uncompressed file path with gzip encoding, bypassing password protections configured for the compressed file. This can lead to unauthorized disclosure of sensitive files. The issue is considered moderate due to its niche configuration requirements and limited exposure in typical Red Hat enterprise environments.