# CVE-2026-88835: BusyBox dpkg read_package_field() out-of-bounds heap read

Source: https://junglewise.ai/threats/cve-2026-88835-busybox-dpkg-read-package-field-steps-past-a-nul-terminator-on  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-23. Updated: 2026-09-26  
License: CC BY 4.0 with a link back

CVE-2026-88835 · Severity: medium · CVSS 6.1 · Published 2026-09-23

BusyBox is a lightweight utility suite used in embedded systems and containers. A vulnerability in its dpkg package processing can be triggered by malformed .deb package files, potentially allowing an attacker to read sensitive data from memory. An attacker would need to supply a crafted .deb package that causes the application to read beyond allocated memory boundaries.

Technologies: [Busybox](https://junglewise.ai/threats/technologies/busybox). Vendors: [Busybox](https://junglewise.ai/threats/vendors/busybox).

## Quick answers

**Is CVE-2026-88835 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-88835 being exploited in the wild.

**How severe is CVE-2026-88835?** Medium severity, with a CVSS score of 6.1, published 23 September 2026.

**Which products and versions are affected?** Busybox prior to 1.37.0-9.1.hum1.

**Is there a fix for CVE-2026-88835?** A patch was published on 2026-09-25. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-88835 attacked?** It is attacked with local access or over the network, in a network appliance.

**Am I affected by CVE-2026-88835?** Check whether you run Busybox at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The vulnerability exists in the read_package_field() function within BusyBox's dpkg implementation, where a NUL terminator check fails on malformed .deb packages, causing an out-of-bounds heap read. The attack requires a local or network-supplied malicious .deb file to be processed. The flaw allows information disclosure by reading unintended heap memory; a fix is available in patched versions.

## Affected products

- BusyBox BusyBox prior to 1.37.0-9.1.hum1

## Timeline

- 2026-09-23: disclosed
- 2026-09-25: patched

## References

- [https://catalog.redhat.com/software/containers/](https://catalog.redhat.com/software/containers/)
- [https://access.redhat.com/errata/RHSA-2026:72111](https://access.redhat.com/errata/RHSA-2026:72111)

## Related threats

- [BusyBox divide-by-zero in volume identification FAT parser](https://junglewise.ai/threats/cve-2026-124742-a-flaw-was-found-in-busybox-the-volume-identification-component)
- [BusyBox httpd stack buffer overflow in subdirectory config](https://junglewise.ai/threats/cve-2026-124739-a-flaw-was-found-in-busybox-when-the-httpd-web-server-processes)
- [BusyBox heap buffer overflow in TFTP client](https://junglewise.ai/threats/cve-2026-124737-a-flaw-was-found-in-busybox-when-the-tftp-trivial-file-transfer)
- [BusyBox libarchive symlink directory traversal arbitrary file creation](https://junglewise.ai/threats/cve-2026-92205-busybox-libarchive-symlink-directory-traversal-arbitrary-file)
- [BusyBox udhcpc integer underflow in DHCP packet processing](https://junglewise.ai/threats/cve-2026-88833-a-flaw-was-found-in-busybox-s-udhcpc-dhcp-client-when-processing)