Linux · SUSE Linux Enterprise · Security advisory · November 7, 2026
SUSE-SU-2026:24215-1: busybox security update
SUSE-SU-2026:24215-1, released November 7, 2026, fixes 7 CVEs in busybox (version 1.37.0-160000.8.1). None of them is reported as exploited. Patch Radar priority: Routine.
Routine
CVEs closed
7
None rated Critical
Exploited
0
None reported
Highest CVSS
6.7
Base score, 0 to 10
Highest EPSS
0.0035
29th percentile
Priority of the 7 CVEs
Patch now 0
Urgent 0
High 0
Routine 7
Fixed package versions
| Product | Release | Fixed in |
|---|---|---|
| busybox | sles 16.0 | 1.37.0-160000.8.1 |
CVEs this fix closes
| Priority | CVE | Title | CVSS | EPSS | Exploitation |
|---|---|---|---|---|---|
| Routine | CVE-2026-88830 | busybox: unit confusion in TLS Montgomery reduction buffer allocation causes a pre-authentication heap buffer | n/a | 0.0035 | None reported |
| Routine | CVE-2026-88837 | busybox: httpd misidentifies yescrypt password hashes as plaintext (bsc#1282552). | n/a | 0.0027 | None reported |
| Routine | CVE-2026-88831 | Busybox: busybox: httpd silently fails open when ip deny rules contain invalid cidr prefix lengths | 5.3 | 0.0024 | None reported |
| Routine | CVE-2026-88832 | Busybox: busybox: romfs volume id parsing performs unbounded memcpy into fixed-size label buffer, causing heap overflow | 6.1 | 0.0013 | None reported |
| Routine | CVE-2026-88839 | Busybox: busybox: passwd/group parser writes heap pointers out of bounds due to stale tokenize() endpoint | 6.7 | 0.0012 | None reported |
| Routine | CVE-2026-88835 | Busybox: busybox: dpkg read_package_field() steps past nul terminator, causing out-of-bounds read on malformed .deb packages | 6.1 | 0.0012 | None reported |
| Routine | CVE-2026-88841 | busybox: OOB read and silent memory corruption of the status file due to `write_status_file()` failing to reset | n/a | n/a | None reported |
Showing 1 to 7 of 7
1
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.