CVE-2026-62259 in Htslibinfo

Summary

by MITRE • 11/20/2026

HTSlib is a library for reading and writing bioinformatics file formats. Prior to 1.21.2, 1.22.3, 1.23.2, and 1.24, the experimental CRAM v4 functions cram_xpack_decode_char and cram_xrle_decode_char do not validate that attacker-controlled decode sizes remain within their expanded input arrays. Crafted CRAM data can therefore make either decoder read beyond the supplied input buffer, potentially disclosing process-state information or crashing the process through invalid memory access. This issue is fixed in versions 1.21.2, 1.22.3, 1.23.2, and 1.24.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Analysis

by VulDB Data Team • 11/20/2026

HTSlib serves as a critical software component within the bioinformatics ecosystem, providing essential functionality for reading and writing various genomic data file formats including SAM, BAM, CRAM, VCF, and BCF. The library is widely adopted by researchers, clinical laboratories, and analytical pipelines to process high-throughput sequencing data. Within this context, the integrity of input parsing routines is paramount because bioinformatics tools frequently ingest large volumes of external data files that may originate from untrusted or compromised sources. A significant security deficiency was identified in the experimental CRAM v4 decoding functions specifically cram_xpack_decode_char and cram_xrle_decode_char prior to versions 1.21.2, 1.22.3, 1.23.2, and 1.24. These functions are responsible for decompressing data encoded using specific algorithms defined in the CRAM v4 specification, which aims to improve compression efficiency over previous iterations of the format.

The core technical flaw lies in a failure to perform adequate bounds checking on decode sizes relative to the supplied input buffers. When processing crafted or maliciously constructed CRAM files, an attacker can manipulate metadata fields that dictate how much data should be read during the decompression process. Because the library did not validate that these decoded sizes remained within the boundaries of the actual available input array, the decoder would proceed to access memory locations beyond the allocated buffer limits. This behavior constitutes a classic out-of-bounds read vulnerability where the application attempts to retrieve information from memory addresses it does not own or should not access according to standard operating system security models.

The operational impact of this vulnerability is severe and multifaceted depending on how HTSlib is integrated into downstream applications. In scenarios where bioinformatics software processes untrusted CRAM files, such as those received via email attachments, public repositories, or compromised sequencing facilities, the immediate consequence can be a denial of service through application crashes caused by invalid memory access exceptions. More critically, out-of-bounds reads allow for potential information disclosure. By carefully crafting input data to trigger specific read patterns, an attacker may be able to leak sensitive process-state information residing in adjacent memory regions. This could include cryptographic keys, user credentials, or other proprietary genomic data currently held in the application's memory space, thereby compromising confidentiality requirements essential for patient privacy and intellectual property protection.

This vulnerability aligns with Common Weakness Enumeration CWE-125 which describes out-of-bounds read conditions resulting from improper validation of input array sizes. From a tactical perspective related to the MITRE ATT&CK framework, this flaw facilitates initial access or reconnaissance phases where adversaries exploit software vulnerabilities to gain footholds in targeted environments or extract sensitive data without detection through standard logging mechanisms if memory corruption does not immediately crash the service. The lack of boundary checks represents a fundamental input validation failure that undermines the security posture of any system relying on HTSlib for CRAM processing.

Mitigation strategies primarily involve upgrading to patched versions of HTSlib, specifically version 1.21.2 or later depending on the branch in use, as these releases include corrections that enforce strict bounds checking before executing decode operations. Organizations utilizing this library should audit their dependency management processes to ensure timely updates are applied across all affected systems and pipelines. Additionally, developers integrating HTSlib into custom applications should implement defense-in-depth measures such as running bioinformatics workloads within sandboxed environments or containers with restricted memory access permissions to limit the blast radius of potential exploits. Input validation at the application layer prior to passing data to the library can also serve as an additional safeguard against malformed CRAM files designed to trigger these decoding routines.

Responsible

GitHub M

Reservation

07/13/2026

Disclosure

11/20/2026

Moderation

accepted

CPE

ready

EPSS

0.00542

KEV

no

Activities

very low

Sources

Interested in the pricing of exploits?

See the underground prices here!