Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-31965: CWE-125: Out-of-bounds Read in samtools htslib

0
Medium
VulnerabilityCVE-2026-31965cvecve-2026-31965cwe-125cwe-129
Published: Wed Mar 18 2026 (03/18/2026, 18:50:37 UTC)
Source: CVE Database V5
Vendor/Project: samtools
Product: htslib

Description

HTSlib is a library for reading and writing bioinformatics file formats. CRAM is a compressed format which stores DNA sequence alignment data. In the `cram_decode_slice()` function called while reading CRAM records, validation of the reference id field occurred too late, allowing two out of bounds reads to occur before the invalid data was detected. The bug does allow two values to be leaked to the caller, however as the function reports an error it may be difficult to exploit them. It is also possible that the program will crash due to trying 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.

AI-Powered Analysis

AILast updated: 03/18/2026, 19:13:43 UTC

Technical Analysis

CVE-2026-31965 is a medium severity vulnerability classified under CWE-125 (Out-of-bounds Read) and CWE-129 (Improper Validation of Array Index) affecting the htslib library, a core component of samtools used for reading and writing bioinformatics file formats, specifically CRAM files which store compressed DNA sequence alignment data. The vulnerability arises in the cram_decode_slice() function, where the validation of the reference ID field occurs too late during the parsing of CRAM records. This delayed validation allows two out-of-bounds memory reads before the function detects the invalid reference ID and returns an error. These out-of-bounds reads can leak two values from memory to the caller, potentially exposing sensitive data. Additionally, the invalid memory access may cause the program to crash, resulting in denial of service. The vulnerability affects htslib versions prior to 1.21.1, versions between 1.22 and 1.22.2, and version 1.23. Fixed versions 1.21.1, 1.22.2, and 1.23.1 address this issue. Exploitation requires no authentication or user interaction and can be triggered remotely by processing maliciously crafted CRAM files. Although no known exploits have been reported in the wild, the flaw poses risks to confidentiality and availability in environments processing genomic data. No workarounds exist, making patching the only effective mitigation.

Potential Impact

The primary impact of CVE-2026-31965 is the potential leakage of sensitive memory contents due to out-of-bounds reads, which could expose confidential genomic data or other sensitive information residing in memory. Additionally, the vulnerability can cause application crashes, leading to denial of service in bioinformatics pipelines that rely on htslib for processing CRAM files. Organizations involved in genomic research, clinical diagnostics, or bioinformatics data processing may face data confidentiality risks and operational disruptions. Since exploitation requires no authentication and can be triggered remotely by supplying crafted CRAM files, attackers could target publicly accessible systems or shared computational resources. Although the vulnerability does not allow code execution or privilege escalation, the confidentiality and availability impacts are significant in sensitive environments handling genomic data. The lack of workarounds increases the urgency for patching to maintain data integrity and service continuity.

Mitigation Recommendations

To mitigate CVE-2026-31965, organizations should immediately update htslib to versions 1.21.1, 1.22.2, 1.23.1, or later, which contain the necessary fixes. Since no workarounds exist, patching is the only reliable defense. Additionally, organizations should audit their bioinformatics pipelines to identify all instances where htslib or samtools are used to ensure comprehensive patch deployment. Implement strict input validation and filtering on CRAM files received from untrusted sources to reduce exposure to crafted malicious files. Employ runtime memory protection mechanisms such as AddressSanitizer or similar tools during development and testing to detect out-of-bounds accesses early. Monitor application logs and system behavior for crashes or anomalies that could indicate exploitation attempts. Finally, maintain an inventory of bioinformatics tools and dependencies to facilitate rapid response to future vulnerabilities.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-03-10T15:40:10.484Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 69baf5d2771bdb1749bce2b2

Added to database: 3/18/2026, 6:58:26 PM

Last enriched: 3/18/2026, 7:13:43 PM

Last updated: 3/18/2026, 8:01:32 PM

Views: 6

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses