CVE-2026-31966: HTSlib CRAM reader has out-of-bounds read due to improper validation of input
HTSlib is a library for reading and writing bioinformatics file formats. CRAM is a compressed format which stores DNA sequence alignment data. As one method of removing redundant data, CRAM uses reference-based compression so that instead of storing the full sequence for each alignment record it stores a location in an external reference sequence along with a list of differences to the reference at that location as a sequence of "features". When decoding CRAM records, the reference data is stored in a char array, and parts matching the alignment record sequence are copied over as necessary. Due to insufficient validation of the feature data series, it was possible to make the cramdecodeseq() function copy data from either before the start, or after the end of the stored reference either into the buffer used to store the output sequence for the cram record, or into the buffer used to build the SAM MD tag. This allowed arbitrary data to be leaked to the calling function. This bug may allow information about program state to be leaked. It may also cause a program crash through an attempt to access invalid memory. Versions 1.23.1, 1.22.2 and 1.21.1 include fixes for this issue. There is no workaround for this issue.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2026-31966?
The severity of CVE-2026-31966 is classified as high due to potential out-of-bounds read vulnerabilities in the HTSlib library.
How do I fix CVE-2026-31966?
To fix CVE-2026-31966, upgrade to HTSlib versions 1.23 or later, which include patches for the identified vulnerability.
What versions of HTSlib are affected by CVE-2026-31966?
HTSlib versions 1.21.1, 1.22.2, and 1.23.1 are affected by CVE-2026-31966.
What type of vulnerability is CVE-2026-31966?
CVE-2026-31966 is characterized as an out-of-bounds read vulnerability due to improper validation of input in the CRAM reader of HTSlib.
Can CVE-2026-31966 lead to data exposure?
Yes, CVE-2026-31966 can potentially lead to data exposure by allowing malicious inputs to read beyond the intended memory bounds.