Heap corruption via stale tokenize endpoint
Published Sep 23, 2026 · Updated Sep 23, 2026
Out-of-bounds write in BusyBox account parsing in Red Hat Hardened Images allows attackers to corrupt heap memory via crafted records. The tokenize() routine retains a stale endpoint after trimming, so group-member pointer placement can extend beyond the allocated buffer. Exploitation requires influence over a parsed passwd or group record; no code-execution or service-level consequence is publicly established.
Summary
What happened
Out-of-bounds write in BusyBox account parsing in Red Hat Hardened Images allows attackers to corrupt heap memory via crafted records. The tokenize() routine retains a stale endpoint after trimming, so group-member pointer placement can extend beyond the allocated buffer. Exploitation requires influence over a parsed passwd or group record; no code-execution or service-level consequence is publicly established.
The record
- CVE
- CVE-2026-88839
- Published
- Sep 23, 2026
- Updated
- Sep 23, 2026
- Vendor
- Commonhaus Foundation
- Product
- Red Hat Hardened Images
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 23, 2026CVE publishedPublication date reported by the CVE source.
- Sep 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started