---
title: "CVE-2026-88832: BusyBox - Buffer Overflow"
description: "BusyBox contains a heap buffer overflow caused by unbounded strlen on attacker-controlled romfs volume ID metadata, letting attackers cause memory corruption via crafted filesystem images, exploit requires crafted filesystem image."
url: https://panop.io/threat-heartbeat/CVE-2026-88832/
---

# CVE-2026-88832 BusyBox - Buffer Overflow

BusyBox contains a heap buffer overflow caused by unbounded strlen on attacker-controlled romfs volume ID metadata, letting attackers cause memory corruption via crafted filesystem images, exploit requires crafted filesystem image.

CVSS base score 7.3 /10

High

CISA KEV

Not listed

Public exploit

None known

Authentication

Required

EPSS

0.13% chance of exploitation in 30 days

[View the NVD record ↗](https://nvd.nist.gov/vuln/detail/CVE-2026-88832)

## Details

Type

Buffer Overflow

Impact

Remote Code Execution

CVSS vector

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

Published

23 September 2026

Updated

15 October 2026

Weakness

[CWE-787](https://cwe.mitre.org/data/definitions/787.html)

## Vendor fix

Update to the latest version of BusyBox.

Patching closes this CVE. It does not tell you which of your systems run the affected version, or what else is exposed alongside them.

## References

- [https://nvd.nist.gov/vuln/detail/CVE-2026-88832](https://nvd.nist.gov/vuln/detail/CVE-2026-88832)
- [https://access.redhat.com/security/cve/CVE-2026-88832](https://access.redhat.com/security/cve/CVE-2026-88832)
- [https://bugzilla.redhat.com/show\_bug.cgi?id=2531345](https://bugzilla.redhat.com/show_bug.cgi?id=2531345)
- [https://access.redhat.com/errata/RHSA-2026:72111](https://access.redhat.com/errata/RHSA-2026:72111)

[← All CVEs](https://panop.io/threat-heartbeat/)

## What this record can't tell you

- Whether you run the affected software, and where
- Whether an attacker can actually reach and exploit it
- The misconfigurations that never get a CVE number
- What it would cost the business, ranked into what to fix first

Panop answers these inside your environment, for this CVE and every other finding.

[Book a demo](https://panop.io/demo)
