CVE-2026-31962
Heap buffer overflow in HTSlib CRAM decoding may lead to code execution.
Is CVE-2026-31962 being exploited?
Not confirmed. CVE-2026-31962 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.36% probability of exploitation in the next 30 days.
How severe is CVE-2026-31962?
CVE-2026-31962 is rated High. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-31962?
Yes. A fix has been recorded for CVE-2026-31962. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-31962 affect?
CVE-2026-31962 affects HTSlib, CRAM decoding component. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-31962?
Upgrade HTSlib to fixed versions (1.23.1+, 1.22.2, or 1.21.1).
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Heap overflow via crafted CRAM file; may crash, corrupt data, or allow arbitrary code execution.
Patch when possible
- affected< 1.21.1
- affected>= 1.22 and < 1.22.2
- affected= 1.23
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.