BusyBox · Out-of-bounds Write
Source GCVE Database
Not known to be exploited · CVSS 7.5 High.
Data as of 11 Nov 2026, 13:32 UTC
Thin evidence
One scorer or none| CNA (redhat) | CVSS 3.1 | 7.5 |
|---|
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation 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
Red Hat recommends preventing untrusted users from creating or modifying configuration files by restricting write permissions on all web root and subdirectory paths served by BusyBox httpd to administrative accounts only (e.g., using 'chmod -R o-w /path/to/webroot'). Additionally, run the BusyBox httpd process under an unprivileged user account by specifying the '-u' flag (e.g., 'busybox httpd -u nobody') to drop elevated privileges. Restarting the daemon is required for these changes to take effect. These mitigations reduce the risk of exploitation by limiting write access and privilege levels.
Description
A stack-based buffer overflow vulnerability exists in BusyBox's httpd web server when processing subdirectory configuration files with an overly long index page name. An attacker with write permissions to these configuration files could exploit this flaw to execute arbitrary code with elevated privileges or cause a denial of service by crashing the server. The vulnerability requires the BusyBox httpd service to be running and serving content from directories writable by untrusted users. Exposure is limited in standard Red Hat environments where BusyBox httpd is not deployed by default.