CVE-2026-88841

busybox: This update for busybox fixes the following issues: - CVE-2026-88830: unit confusion in TLS Montgomery reduction buf...

CVE-2026-88841 is fixed in busybox on 1 platform, first by SUSE-SU-2026:4760-1, released November 7, 2026. It is not reported as exploited. Patch Radar priority: Routine.

Routine
CVSS
n/a
No vendor severity
Exploitation
None reported
No vendor assessment
CISA KEV
Not listed
Not in the Known Exploited Vulnerabilities catalog
EPSS
n/a

This update for busybox fixes the following issues: - CVE-2026-88830: unit confusion in TLS Montgomery reduction buffer allocation causes a pre-authentication heap buffer overflow when processing a crafted `ClientKeyExchange` message (bsc#1282575). - CVE-2026-88831: httpd silently fails open when IP deny rules contain invalid CIDR prefix lengths (bsc#1282550). - CVE-2026-88832: romfs volume ID parsing uses unbounded `strlen` on attacker-controlled metadata and allows for a heap buffer overflow when crafted filesystem images are processed (bsc#1282576). - CVE-2026-88835: dpkg read_package_field() steps past NUL terminator, causing out-of-bounds read on malformed .deb packages (bsc#1282551). - CVE-2026-88837: httpd misidentifies yescrypt password hashes as plaintext (bsc#1282552). - CVE-2026-88839: passwd/group parser writes heap pointers out of bounds due to stale tokenize() endpoint (bsc#1282568). - CVE-2026-88841: OOB read and silent memory corruption of the status file due to `write_status_file()` failing to reset the `field_start` cursor between package stanzas (bsc#1282653).

Where it's fixed

ProductFixed inFixReleased
Linux
busybox · opensuse-leap 16.0 1.37.0-160000.8.1 OPENSUSE-SU-2026:22067-1 Nov 7, 2026
busybox · sles 15.7 1.37.0-150700.18.24.1 SUSE-SU-2026:4760-1 Nov 7, 2026
busybox · sles 16.0 1.37.0-160000.8.1 SUSE-SU-2026:24215-1 Nov 7, 2026

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.