Evidence used
- No CISA KEV confirmation is currently recorded.
BlackTreeCVE IntelligenceAuthoritative vendor disclosure · 2026
CVE-2026-88841High confidence
busybox: busybox: dpkg write_status_file() stale cursor causes out-of-bounds read and status file corruption
Red Hat Product Security · busybox-0:1.37.0-9.2.hum1@aarch64 as a component of Red Hat Hardened Images
3.3LowCVSS 3.1
Patch only the product branches with a verified fix
Fix availability varies by productRed Hat Product Security has published authoritative product evidence for this CVE. Validate applicability and follow the linked vendor advisory while canonical CVE data is pending. Verified remediation exists for at least one product or source, but 71 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityLow→Operational priority:Low, unchanged from published severity.unchanged
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict local access and enforce least privilege on affected hosts.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs Red Hat Product Security busybox-0:1.37.0-9.2.hum1@aarch64 as a component of Red Hat Hardened Images and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Remediation availability differs by product scope
Verified remediation exists for at least one product or source, but 71 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
- SUSE Product Security Team: 67 affected or under-investigation product states without a fixed product state in the same current advisory
- Debian Security Tracker: 4 affected package states with no published fix
Distribution package intelligence
5 package statesRelease-specific package status
Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
Package result overrides the generic status
BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 4 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.
Repository candidate not checked
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Debian trixietrixie · source | busybox | Affected, no fix publishedDebian currently tracks this release as open. | Not published in this feed | Debian Security Tracker ↗Source updated 4 Oct 2026 |
| Debian bookwormbookworm · source | busybox | Affected, no fix publishedDebian currently tracks this release as open. | Not published in this feed | Debian Security Tracker ↗Source updated 4 Oct 2026 |
| Debian forkyforky · source | busybox | Affected, no fix publishedDebian currently tracks this release as open. | Not published in this feed | Debian Security Tracker ↗Source updated 4 Oct 2026 |
| Debian sidsid · source | busybox | Affected, no fix publishedDebian currently tracks this release as open. | Not published in this feed | Debian Security Tracker ↗Source updated 4 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | busybox | Under evaluationCanonical reports that the package might be affected and still needs evaluation or fixing. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 4 Oct 2026 |
Direct vendor intelligence
2 currentAuthoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
CVE-2026-88841 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitybusybox: busybox: dpkg write_status_file() stale cursor causes out-of-bounds read and status file corruption
The vendor explicitly identifies these products or versions as containing the fix.
- busybox-0:1.37.0-9.2.hum1@aarch64 as a component of Red Hat Hardened Images
- busybox-0:1.37.0-9.2.hum1@src as a component of Red Hat Hardened Images
- busybox-0:1.37.0-9.2.hum1@x86_64 as a component of Red Hat Hardened Images
- busybox-petitboot-0:1.37.0-9.2.hum1@aarch64 as a component of Red Hat Hardened Images
- busybox-petitboot-0:1.37.0-9.2.hum1@x86_64 as a component of Red Hat Hardened Images
- busybox-shared-0:1.37.0-9.2.hum1@aarch64 as a component of Red Hat Hardened Images
- busybox-shared-0:1.37.0-9.2.hum1@x86_64 as a component of Red Hat Hardened Images
- Summary
- BusyBox dpkg write_status_file() does not reset a stale field cursor between package stanzas, causing out-of-bounds reads and status file corruption when removing multiple packages.
- Remediation
- For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
CVE-2026-88841 · CSAF 2.0 · revision 2 · interimSUSE Product Security TeamCVE-2026-88841
The vendor explicitly identifies these products as affected by this CVE.
- busybox as component of SUSE Linux Enterprise Desktop 15 SP7
- busybox-static as component of SUSE Linux Enterprise Desktop 15 SP7
- busybox as component of SUSE Linux Enterprise High Performance Computing 12 SP5
- busybox as component of SUSE Linux Enterprise High Performance Computing 15 SP1
- busybox as component of SUSE Linux Enterprise High Performance Computing 15 SP2
- busybox as component of SUSE Linux Enterprise High Performance Computing 15 SP3
- busybox as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
- busybox-static as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
- busybox as component of SUSE Linux Enterprise High Performance Computing 15 SP4
- busybox-static as component of SUSE Linux Enterprise High Performance Computing 15 SP4
- busybox as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
- busybox-static as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
- Summary
- unknown
- Remediation
- No remediation text is recorded.
Red Hat Product Security has published authoritative product evidence for this CVE. Validate applicability and follow the linked vendor advisory while canonical CVE data is pending. Verified remediation exists for at least one product or source, but 71 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Fix availability varies by product01
What, why and how
BusyBox dpkg write_status_file() does not reset a stale field cursor between package stanzas, causing out-of-bounds reads and status file corruption when removing multiple packages.
What
BusyBox dpkg write_status_file() does not reset a stale field cursor between package stanzas, causing out-of-bounds reads and status file corruption when removing multiple packages.
Why
The product reads data past the end, or before the beginning, of the intended buffer.
How
An attacker operating through local access may attempt exploitation without authentication after a user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
BusyBox dpkg write_status_file() does not reset a stale field cursor between package stanzas, causing out-of-bounds reads and status file corruption when removing multiple packages.
Why
The product reads data past the end, or before the beginning, of the intended buffer.
How
An attacker operating through local access may attempt exploitation without authentication after a user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- local access → Out-of-bounds Read → cause the confidentiality, integrity or availability impact described by the vendor
- Attack surface
- Local
- Privileges required
- None: unauthenticated exploitation is possible
- User interaction
- Required interaction required
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-125 ↗
CWE-125: Out-of-bounds Read. The product reads data past the end, or before the beginning, of the intended buffer.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:NCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.ILowIntegrity impact: A successful attack can cause a limited loss.ANoneAvailability impact: No direct loss is represented by this metric.- Post-exploitation / living off the land
- The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Fix availability varies by product
- Affected
- The vendor advisory identifies this CVE but does not provide a concise affected-product range.
- Fixed
- busybox-0:1.37.0-9.2.hum1@aarch64 as a component of Red Hat Hardened Images
- busybox-0:1.37.0-9.2.hum1@src as a component of Red Hat Hardened Images
- busybox-0:1.37.0-9.2.hum1@x86_64 as a component of Red Hat Hardened Images
- busybox-petitboot-0:1.37.0-9.2.hum1@aarch64 as a component of Red Hat Hardened Images
- busybox-petitboot-0:1.37.0-9.2.hum1@x86_64 as a component of Red Hat Hardened Images
- busybox-shared-0:1.37.0-9.2.hum1@aarch64 as a component of Red Hat Hardened Images
- busybox-shared-0:1.37.0-9.2.hum1@x86_64 as a component of Red Hat Hardened Images
- Action
- Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
- Workaround
- No separate vendor workaround is recorded. Follow the linked advisory and validate the exact affected product and release.
Official vendor articles1 stored document
Linked articles are downloaded and versioned as source evidence. A CVE mention or approved update relationship does not, by itself, verify a fix for every product branch.
- CVE-2026-88841 - Red Hat Customer Portal →Original publisher ↗Searchable text snapshot · Captured 26 Sep 2026CVE-2026-88841 Description BusyBox dpkg write_status_file() does not reset a stale field cursor between package stanzas, causing out-of-bounds reads and status file corruption when removing multiple packages. Statement This flaw allows a crafted sequence of package removals to corrupt the BusyBox dpkg status file. Fedo
04
Evidence and provenance
Published 23 Sept 2026 · Last source change 29 Sept 2026, 22:37 UTC · CWE-125 · Out-of-bounds Read
CVE recordRed Hat Product Security · OASIS CSAF 2.0
CVSS sourceOther authority
EPSS source Unavailable
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceNo official EUVD mapping
Product sourceAuthoritative vendor CSAF advisory
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD status unavailable
Missing structured fields: official CVE record, canonical affected-version range. Missing data is not evidence of low risk; review the primary advisory.
Material change intelligence
View recent updates ↗What changed after publication
- Affected versionsThe structured affected or fixed version information changed.Red Hat Product Security ↗
- Before
- The vendor advisory identifies this CVE but does not provide a concise affected-product range. · Fixed: busybox-0:1.37.0-9.2.hum1@aarch64 as a component of Red Hat Hardened Images; busybox-0:1.37.0-9.2.hum1@src as a component of Red Hat Hardened Images; busybox-0:1.37.0-9.2.hum1@x86_64 as a component of Red Hat Hardened Images; busybox-petitboot-0:1.37.0-9.2.hum1@aarch64 as a component of Red Hat Hardened Images; busybox-petitboot-0:1.37.0-9.2.hum1@x86_64 as a component of Red Hat Hardened Images; busybox-shared-0:1.37.0-9.2.hum1@aarch64 as a component of Red Hat Hardened Images; busybox-shared-0:1.37.0-9.2.hum1@x86_64 as a component of Red Hat Hardened Images
- After
- The vendor advisory identifies this CVE but does not provide a concise affected-product range. · Fixed: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
- Vendor guidanceAuthoritative vendor guidance changed: added patch: access.redhat.com/CVE-2026-88841; removed mitigation: access.redhat.com/CVE-2026-88841.vendor-csaf:red-hat ↗
- Before
- mitigation: access.redhat.com/CVE-2026-88841 · remediation: access.redhat.com/CVE-2026-88841
- After
- patch: access.redhat.com/CVE-2026-88841 · remediation: access.redhat.com/CVE-2026-88841
- Affected versionsThe structured affected or fixed version information changed.Authoritative vendor CSAF advisory ↗
- Before
- busybox.src as a component of Red Hat Hardened Images · Fixed: No fixed product state is explicitly recorded in the vendor advisory.
- After
- The vendor advisory identifies this CVE but does not provide a concise affected-product range. · Fixed: busybox-0:1.37.0-9.2.hum1@aarch64 as a component of Red Hat Hardened Images; busybox-0:1.37.0-9.2.hum1@src as a component of Red Hat Hardened Images; busybox-0:1.37.0-9.2.hum1@x86_64 as a component of Red Hat Hardened Images; busybox-petitboot-0:1.37.0-9.2.hum1@aarch64 as a component of Red Hat Hardened Images; busybox-petitboot-0:1.37.0-9.2.hum1@x86_64 as a component of Red Hat Hardened Images; busybox-shared-0:1.37.0-9.2.hum1@aarch64 as a component of Red Hat Hardened Images; busybox-shared-0:1.37.0-9.2.hum1@x86_64 as a component of Red Hat Hardened Images
- Remediation statusRemediation status changed from Mitigation available to Patch available.vendor-csaf:red-hat ↗
- Before
- Mitigation available
- After
- Patch available
- Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2026-88841 to remediation: access.redhat.com/CVE-2026-88841.Red Hat Product Security ↗
- Before
- remediation: access.redhat.com/CVE-2026-88841
- After
- remediation: access.redhat.com/CVE-2026-88841
- Remediation statusRemediation status changed from Mitigation available to Patch available.Red Hat Product Security ↗
- Before
- Mitigation available
- After
- Patch available
- Affected versionsThe structured affected or fixed version information changed.Red Hat Product Security ↗
- Before
- busybox.src as a component of Red Hat Hardened Images
- After
- Fixed: busybox-0:1.37.0-9.2.hum1@aarch64 as a component of Red Hat Hardened Images; busybox-0:1.37.0-9.2.hum1@src as a component of Red Hat Hardened Images; busybox-0:1.37.0-9.2.hum1@x86_64 as a component of Red Hat Hardened Images; busybox-petitboot-0:1.37.0-9.2.hum1@aarch64 as a component of Red Hat Hardened Images; busybox-petitboot-0:1.37.0-9.2.hum1@x86_64 as a component of Red Hat Hardened Images; busybox-shared-0:1.37.0-9.2.hum1@aarch64 as a component of Red Hat Hardened Images; busybox-shared-0:1.37.0-9.2.hum1@x86_64 as a component of Red Hat Hardened Images
- Catalogue recordCVE added to the BlackTree catalogue.Authoritative vendor CSAF advisory ↗
Vendor disclosed CVE identifier
Vendor remediation published
Fixed release recorded from official guidance
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.