# CVE-2026-88832: Busybox: busybox: romfs volume id parsing performs unbounded memcpy into fixed-size label buffer, causing heap overflow

> Attackers can trigger a heap buffer overflow in BusyBox romfs parsing via crafted filesystem images, potentially leading to code execution or crashes.

- **Severity:** High 7.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 23 Sep 2026
- **Updated:** 25 Sep 2026
- **Also known as:** AZL-105128, DEBIAN-CVE-2026-88832, ECHO-b60b-adf0-72ff, GHSA-hqw2-f49w-7w56, UBUNTU-CVE-2026-88832

## What is CVE-2026-88832?

CVE-2026-88832 is a high-severity memory corruption vulnerability in Red Hat Hardened Images, published on 23 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

BusyBox romfs volume ID parsing uses unbounded strlen on attacker-controlled metadata, causing a heap buffer overflow when processing crafted filesystem images.

Weakness: CWE-787 (Out-of-bounds Write)

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


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

Apply the vendor's patch.

## Is CVE-2026-88832 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-88832 is a high-severity memory corruption vulnerability in Red Hat Hardened Images, published on 23 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-88832 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-88832/ (Markdown: https://insights.sbomify.com/CVE-2026-88832/index.md)
```

## Sources

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

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