CVE-2026-42250

MEDIUMPre-NVD 4.84.8
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 97% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
4.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.8Exploit: None knownExposed: 0

A fix is available — apply it.

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

CVSS v3
4.8
EG Score
4.8(medium)
EG Risk
22(Track)
EG Risk 22/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity48% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

May 28, 2026

Last Modified

June 5, 2026

Advisory Details (4)

Auto-updated Jun 15, 2026
No patch confirmed yet.
generic

[PATCH] bzip2recover: Make sure to not process more than BZ_MAX_HANDLED_BLOCKS - Mark Wielaard

https://inbox.sourceware.org/bzip2-devel/[email protected]/
generic

Vulnerability in bzip2 software | CERT Polska

https://cert.pl/en/posts/2026/05/CVE-2026-42250/

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatbzip2-main-1.0.8-23.2.hum12026-06-26redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
bzip21.0.8-4, 1.0.8-5, 1.0.8-5.1, 1.0.8-6
Debian:12(1)
PackageVulnerable rangeFixed inDependents
bzip21.0.8-5, 1.0.8-5.1, 1.0.8-6
Debian:13(1)
PackageVulnerable rangeFixed inDependents
bzip21.0.8-6
Debian:14(1)
PackageVulnerable rangeFixed inDependents
bzip21.0.8-6

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 4× in last 7d / 71× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 229 total refreshes for this CVE.

  1. 2026-09-04 05:06 UTCEPSS rescore
  2. 2026-09-01 13:54 UTCEPSS rescore
  3. 2026-08-30 19:17 UTCEPSS rescore
  4. 2026-08-30 01:22 UTCEPSS rescore
  5. 2026-08-28 21:41 UTCEPSS rescore
  6. 2026-08-27 14:25 UTCEPSS rescore
  7. 2026-08-26 14:46 UTCEPSS rescore
  8. 2026-08-25 13:49 UTCEPSS rescore
  9. 2026-08-25 04:45 UTCEG score recompute
  10. 2026-08-25 04:45 UTCVendor advisory
  11. 2026-08-25 04:45 UTCGHSA enrichment
  12. 2026-08-23 14:31 UTCEG score recompute
  13. 2026-08-23 14:31 UTCVendor advisory
  14. 2026-08-23 14:31 UTCGHSA enrichment
  15. 2026-08-23 00:19 UTCEPSS rescore
  16. 2026-08-21 23:49 UTCEPSS rescore
  17. 2026-08-21 15:26 UTCEG score recompute
  18. 2026-08-21 15:26 UTCVendor advisory
  19. 2026-08-21 15:26 UTCGHSA enrichment
  20. 2026-08-20 22:55 UTCEPSS rescore
  21. 2026-08-20 10:47 UTCEG score recompute
  22. 2026-08-20 10:47 UTCVendor advisory
  23. 2026-08-20 10:47 UTCGHSA enrichment
  24. 2026-08-19 17:03 UTCEPSS rescore
  25. 2026-08-18 13:48 UTCEPSS rescore
Show 75 more
  1. 2026-08-17 13:47 UTCEPSS rescore
  2. 2026-08-17 08:17 UTCEG score recompute
  3. 2026-08-17 08:17 UTCVendor advisory
  4. 2026-08-17 08:17 UTCGHSA enrichment
  5. 2026-08-16 14:56 UTCEPSS rescore
  6. 2026-08-16 02:35 UTCEG score recompute
  7. 2026-08-16 02:35 UTCVendor advisory
  8. 2026-08-16 02:35 UTCGHSA enrichment
  9. 2026-08-16 02:14 UTCEPSS rescore
  10. 2026-08-15 03:46 UTCEG score recompute
  11. 2026-08-15 03:46 UTCVendor advisory
  12. 2026-08-15 03:46 UTCGHSA enrichment
  13. 2026-08-15 01:30 UTCEPSS rescore
  14. 2026-08-14 05:54 UTCEG score recompute
  15. 2026-08-14 05:54 UTCVendor advisory
  16. 2026-08-14 05:54 UTCGHSA enrichment
  17. 2026-08-13 22:00 UTCEPSS rescore
  18. 2026-08-13 08:02 UTCEG score recompute
  19. 2026-08-13 08:02 UTCVendor advisory
  20. 2026-08-13 08:02 UTCGHSA enrichment
  21. 2026-08-12 13:51 UTCEPSS rescore
  22. 2026-08-12 09:59 UTCEG score recompute
  23. 2026-08-12 09:59 UTCVendor advisory
  24. 2026-08-12 09:59 UTCGHSA enrichment
  25. 2026-08-11 13:43 UTCEPSS rescore
  26. 2026-08-11 12:06 UTCEG score recompute
  27. 2026-08-11 12:06 UTCVendor advisory
  28. 2026-08-11 12:06 UTCGHSA enrichment
  29. 2026-08-11 00:00 UTCEPSS rescore
  30. 2026-08-10 14:07 UTCVendor advisory
  31. 2026-08-10 14:07 UTCGHSA enrichment
  32. 2026-08-09 16:15 UTCEG score recompute
  33. 2026-08-09 16:15 UTCVendor advisory
  34. 2026-08-09 16:15 UTCGHSA enrichment
  35. 2026-08-09 13:46 UTCEPSS rescore
  36. 2026-08-08 18:24 UTCEG score recompute
  37. 2026-08-08 18:24 UTCVendor advisory
  38. 2026-08-08 18:24 UTCGHSA enrichment
  39. 2026-08-08 16:37 UTCEPSS rescore
  40. 2026-08-07 17:23 UTCEG score recompute
  41. 2026-08-07 17:23 UTCVendor advisory
  42. 2026-08-07 17:23 UTCGHSA enrichment
  43. 2026-08-06 19:31 UTCEG score recompute
  44. 2026-08-06 19:31 UTCVendor advisory
  45. 2026-08-06 19:31 UTCGHSA enrichment
  46. 2026-08-06 13:46 UTCEPSS rescore
  47. 2026-08-05 21:39 UTCEG score recompute
  48. 2026-08-05 21:39 UTCVendor advisory
  49. 2026-08-05 21:39 UTCGHSA enrichment
  50. 2026-08-05 19:17 UTCEPSS rescore
  51. 2026-08-04 23:47 UTCEG score recompute
  52. 2026-08-04 23:47 UTCVendor advisory
  53. 2026-08-04 23:47 UTCGHSA enrichment
  54. 2026-08-04 15:10 UTCEPSS rescore
  55. 2026-08-04 10:38 UTCEPSS rescore
  56. 2026-08-03 16:11 UTCVendor advisory
  57. 2026-08-03 16:11 UTCGHSA enrichment
  58. 2026-08-02 12:27 UTCEG score recompute
  59. 2026-08-02 12:27 UTCVendor advisory
  60. 2026-08-02 12:27 UTCGHSA enrichment
  61. 2026-08-02 02:27 UTCEPSS rescore
  62. 2026-08-01 14:35 UTCEG score recompute
  63. 2026-08-01 14:35 UTCVendor advisory
  64. 2026-08-01 14:35 UTCGHSA enrichment
  65. 2026-08-01 04:16 UTCEPSS rescore
  66. 2026-07-31 06:21 UTCEG score recompute
  67. 2026-07-31 06:21 UTCVendor advisory
  68. 2026-07-31 06:21 UTCGHSA enrichment
  69. 2026-07-30 16:28 UTCEPSS rescore
  70. 2026-07-30 01:30 UTCEPSS rescore
  71. 2026-07-29 14:17 UTCEG score recompute
  72. 2026-07-29 14:17 UTCVendor advisory
  73. 2026-07-29 14:17 UTCGHSA enrichment
  74. 2026-07-28 15:36 UTCEPSS rescore
  75. 2026-07-27 14:13 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-42250?
CVE-2026-42250 is a medium vulnerability published on May 28, 2026. 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…
When was CVE-2026-42250 disclosed?
CVE-2026-42250 was first published in the National Vulnerability Database on May 28, 2026, with the most recent update on June 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-42250 actively exploited?
CVE-2026-42250 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.4% of all scored CVEs.
What is the CVSS score of CVE-2026-42250?
CVE-2026-42250 has a CVSS v3 base score of 4.8 (NVD).
How do I remediate CVE-2026-42250?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-42250, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-42250

Explore →

Is Your Infrastructure Affected by CVE-2026-42250?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.