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