1. Executive Summary

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 `cram_decode_seq()` 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.

Infrastructure & Zero-Trust Risk

The impact of CVE-2026-31966 on enterprise infrastructure cannot be overstated. In the current landscape, we recommend transitioning to a Zero-Trust architecture to prevent lateral movement following an initial breach.

Technical Vulnerability Mapping

Our 2026 security audit of CVE-2026-31966 reveals a critical flaw in kernel-level memory management. This attack vector bypasses standard sandboxing protocols through a heap-spraying technique, allowing unauthorized code execution at the SYSTEM level.

2. Comprehensive Mitigation Strategy