CVE-2026-42250: Off-by-One Leading to Out-of-Bounds Write in bzip2
bzip2 contains an off‑by‑one error in the bzip2recover utility. When processing a specially crafted file, the application performs an out‑of‑bounds write to a global buffer, resulting in memory corruption and a crash (denial of service).
This issue was fixed in bzip2 patch 35d122a3df8b0cc4082a4d89fdc6ee99f375fe67
Security readout for executives and security teams
Plain-English summary
CVE-2026-42250 is a denial-of-service flaw in bzip2recover, a recovery utility included with bzip2. A specially crafted file can trigger memory corruption and crash the tool. Business impact is likely limited unless users or automated workflows process untrusted bzip2 files with bzip2recover.
Executive priority
Treat as a routine patching item unless bzip2recover is used in exposed or automated workflows. Prioritize systems that process external files, but this is not currently supported as an active-exploitation emergency by the provided sources.
Technical view
The issue is an off-by-one error causing an out-of-bounds write to a global buffer in bzip2recover. The CVE maps to CWE-787 and has CVSS 4.0 score 4.8. The source bundle states it is fixed by bzip2 commit 35d122a3df8b0cc4082a4d89fdc6ee99f375fe67.
Likely exposure
Exposure is most likely on systems where bzip2recover is installed and used against files from untrusted sources. The CVSS vector indicates local attack requirements and user interaction. Package-level affected version details are not provided in the sources.
Exploitation context
Sources describe a crafted-file crash and denial of service, not code execution. The source bundle says KEV is false, and no provided source reports active exploitation. Practical risk depends on whether bzip2recover is reachable in user workflows, support processes, or automated file recovery pipelines.
Researcher notes
The available data supports a local, user-assisted denial-of-service condition in bzip2recover. The patch reference is available, but package-specific affected and fixed versions are incomplete. Avoid assuming impact beyond crash/memory corruption without additional vendor analysis.
Mitigation direction
Apply vendor or distribution updates that include commit 35d122a3df8b0cc4082a4d89fdc6ee99f375fe67.
Avoid processing untrusted compressed files with bzip2recover until updated.
Check OS vendor advisories for fixed package versions.
Restrict use of bzip2recover in automated workflows handling external files.
Validation and detection
Inventory systems with bzip2 and bzip2recover installed.
Verify whether installed source or package includes the referenced fix commit.
Review file-processing workflows for bzip2recover use on untrusted inputs.
Monitor vendor and distribution advisories for package-specific remediation status.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-787: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-787 · source CWE mapping
Out-of-bounds Write
Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.