# CVE-2026-88837: Busybox: busybox: httpd misidentifies yescrypt password hashes as plaintext, inverting authentication

> BusyBox httpd incorrectly treats yescrypt password hashes as plaintext, allowing attackers to bypass Basic Authentication.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/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:** 23 Sep 2026
- **Updated:** 25 Sep 2026
- **Also known as:** BELL-CVE-2026-88837, DEBIAN-CVE-2026-88837, ECHO-f105-a15f-8af6, GHSA-f9qv-fq2p-pvch, UBUNTU-CVE-2026-88837

## What is CVE-2026-88837?

CVE-2026-88837 is a medium-severity authentication bypass vulnerability in Red Hat Hardened Images, published on 23 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

BusyBox httpd treats yescrypt ($y$) password hashes as plaintext during Basic Authentication, inverting the authentication check.

Weakness: CWE-305 (Authentication Bypass by Primary Weakness)

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


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

Apply the vendor's patch.

## Is CVE-2026-88837 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-88837 is a medium-severity authentication bypass vulnerability in Red Hat Hardened Images, published on 23 Sep 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-88837 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-88837/ (Markdown: https://insights.sbomify.com/CVE-2026-88837/index.md)
```

## Sources

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

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