Skip to content
Fencer Intel
low 3.3

CVE-2026-88842 json

Busybox: busybox: dpkg stale field_start pointer causes out-of-bounds read and status file corruption

published 28d ago modified 27d ago also EUVD-2026-100957

cvss
3.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 4%
public exploits
0
none known

Summary

A flaw was found in BusyBox dpkg. The write_status_file() function does not reset a field cursor between package stanzas. When two packages are removed in a single invocation and the first stanza is larger than the second, the second package stanza can be dropped from the status file, causing limited data corruption.

Patch / fix

  • Red Hat Red Hat Hardened Images 1.37.0-9.4.hum1
  • busybox hummingbird 1 1.37.0-9.4.hum1
  • busybox-shared hummingbird 1 1.37.0-9.4.hum1
  • busybox-petitboot hummingbird 1 1.37.0-9.4.hum1

red hat advisories RHSA-2026:81391

  • busybox openSUSE Tumbleweed 1.38.0-4.1

opensuse advisories openSUSE-SU-2026:12376-1

Is CVE-2026-88842 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-88842 updated cvss 3.3

busybox: busybox: dpkg stale field_start pointer causes out-of-bounds read and status file corruption

  • Red Hat Hardened Images busybox 1.37.0-9.4.hum1, busybox-shared 1.37.0-9.4.hum1, busybox-petitboot 1.37.0-9.4.hum1
    fixed: vendor fix RHSA-2026:81391

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
28d ago

Exploit prediction

0.16% chance of exploitation in the next 30 days, higher than 4% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 3.3 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Affected products

  • Red Hat Red Hat Hardened Images

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.