# CVE-2026-88834: Busybox: busybox: httpd user existence oracle in non-default shadow-disabled builds

> An attacker can enumerate valid usernames in BusyBox httpd when system password authentication is enabled in non-default builds.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** AZL-108318, BELL-CVE-2026-88834, DEBIAN-CVE-2026-88834, GHSA-g83p-qwfp-8p23, UBUNTU-CVE-2026-88834

## What is CVE-2026-88834?

CVE-2026-88834 is a low-severity vulnerability in Red Hat Hardened Images, published on 13 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-203 (Observable Discrepancy)

## Which versions are affected by CVE-2026-88834?


## How do I fix CVE-2026-88834?

Apply the vendor's patch.

## Is CVE-2026-88834 being exploited?

There is no known exploitation of CVE-2026-88834 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-88834 and fix it if it is affected.

What it is: CVE-2026-88834 is a low-severity vulnerability in Red Hat Hardened Images, published on 13 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-88834 in the wild and no public exploit code.

Affected product: Red Hat Hardened Images. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-88834/ (Markdown: https://insights.sbomify.com/CVE-2026-88834/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-88834
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-88834
- OSV: https://osv.dev/vulnerability/CVE-2026-88834

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-88834/
Summaries are generated and may contain mistakes; the official description above is the record.