VulnerabilityPublished 13 Oct 2026Updated 28 Oct 2026

CVE-2026-88834: BusyBox's httpd web server

Affects busyboxSource GCVE Database

Authoritative record:CVE-2026-88834· Low 3.7

Not known to be exploited · CVSS 3.7 Low.

Data as of 28 Oct 2026, 22:28 UTC

CVSS 3.1 base score

3.7Low

How severe the flaw is on the 0–10 CVSS scale.

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: High
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 13 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Ubuntu 26.10busybox`pkg:deb/ubuntu/busybox?arch=source&distro=stonking`Other threats	Affected 1:1.37.0-7ubuntu1 – 1:1.38.0-3ubuntu4 6 affected builds	Fixed in–
Ubuntu 26.04 LTSbusybox`pkg:deb/ubuntu/busybox?arch=source&distro=resolute`Other threats	Affected =1:1.37.0-4ubuntu1 =1:1.37.0-7ubuntu1	Fixed in–
Ubuntu 24.04 LTSbusybox`pkg:deb/ubuntu/busybox?arch=source&distro=noble`Other threats	Affected 1:1.36.1-3ubuntu1 – 1:1.36.1-6ubuntu3.1 4 affected builds	Fixed in–
Ubuntu 22.04 LTSbusybox`pkg:deb/ubuntu/busybox?arch=source&distro=jammy`Other threats	Affected 1:1.30.1-6ubuntu3 – 1:1.30.1-7ubuntu3.1 5 affected builds	Fixed in–
Ubuntu 20.04 LTSbusybox`pkg:deb/ubuntu/busybox?arch=source&distro=focal`Other threats	Affected 1:1.30.1-4ubuntu4 – 1:1.30.1-4ubuntu6.5 8 affected builds	Fixed in–
Ubuntu Pro 18.04 LTSbusybox`pkg:deb/ubuntu/busybox?arch=source&distro=esm-infra/bionic`Other threats	Affected 1:1.22.0-19ubuntu2 – 1:1.27.2-2ubuntu3.4+esm1 10 affected builds	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

A flaw was found in BusyBox's httpd web server. When configured with system password authentication, a user existence oracle may exist in certain build configurations. An attacker could distinguish existing from non-existing usernames by observing authentication failure behavior. Impact is limited to username enumeration and requires non-default compile options or uncommon password file states; default BusyBox builds with shadow password support are not affected.

References

Community reviews

Loading reviews…