HTSlib is a library for reading and writing bioinformatics file formats. CRAM is a compressed format which stores DNA sequence alignment data. While most alignment records store DNA sequence and quality values, the format also allows them to omit this data in certain cases to save space. Due to some quirks of the CRAM format, it is necessary to handle these records carefully as they will actually store data that needs to be consumed and then discarded. Unfortunately the cram_decode_seq() did not handle this correctly in some cases. Where this happened it could result in reading a single byte from beyond the end of a heap allocation, followed by writing a single attacker-controlled byte to the same location. Exploiting this bug causes a heap buffer overflow. If a user opens a file crafted to exploit this issue, it could lead to the program crashing, or overwriting of data and heap structures in ways not expected by the program. It may be possible to use this to obtain arbitrary code execution. Versions 1.23.1, 1.22.2 and 1.21.1 include fixes for this issue. There is no workaround for this issue.
CVE-2026-31962
This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). 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).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.8
- EG Score
- 8.8(low)
- EG Risk
- 44(Track)EG Risk 44/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 computedSeverity88% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
March 18, 2026
Last Modified
June 17, 2026
Advisory Details (2)
Auto-updated Jul 27, 2026Heap buffer overflow in HTSlib CRAM reader due to improper validation of input · Advisory · samtools/htslib · GitHub
https://github.com/samtools/htslib/security/advisories/GHSA-xxmp-v7h3-gpwpcommit d799b54c6401 (samtools/htslib)
Patch available: samtools/htslib 1.23.1 (contains commit d799b54c6401)
https://github.com/samtools/htslib/commit/d799b54c6401879187bba4741be83ff590ac73e3Weakness Classification(4)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 2× in last 7d / 2× 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.
- 2026-07-27 14:41 UTCEG score recompute
- 2026-07-27 14:27 UTCOSV refresh
Related CVEs(same CWE)
Same CWE
10 shownCWE-125 · CWE-787 · CWE-122
- CVE-2009-2523EG 10.0EPSS p98HIGH
- CVE-2004-0978EG 10.0EPSS p98HIGH
- CVE-2004-1287EG 10.0EPSS p97HIGH
- CVE-2004-0574EG 10.0EPSS p99HIGH
- CVE-2002-2227EG 10.0HIGH
- CVE-2006-10003EG 9.8CRITICAL
- CVE-2006-10002NVD 7.5EG 9.8CRITICAL
- CVE-2007-0158EG 9.8CRITICAL
- CVE-2007-0899EG 9.8CRITICAL
- CVE-1999-0006EG 9.8EPSS p96CRITICAL
Frequently asked(4)
What is CVE-2026-31962?
When was CVE-2026-31962 disclosed?
What is the CVSS score of CVE-2026-31962?
How do I remediate CVE-2026-31962?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-31962
Is Your Infrastructure Affected by CVE-2026-31962?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.