HTSlib heap overflow in CRAM v4 decoder may allow code execution
Affects HTSlib before 1.21.2, 1.22.0 to 1.22.2, and 1.23.0 to 1.23.1 when decoding CRAM v4 files with the experimental XPACK or XRLE decoders. Fixed in 1.21.2, 1.22.3 and 1.23.2.
- Exploited
- No known exploitation
- Fix
- Fixed in 1.21.2, 1.22.3, 1.23.2
- Who is exposed
- Specific setups only
Summary
HTSlib, a library for reading and writing bioinformatics file formats, has a heap memory overflow in its experimental CRAM v4 decoder. An attacker can trigger it remotely, without logging in or any user action, by supplying a crafted file, which may crash the program or corrupt heap memory in a way that could allow arbitrary code execution.
Written by a model
Original description
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 XPACK and XRLE decoders cache expanded block pointers at indexes beyond the 512-element slice->block_by_id array. An array index partially controlled by data in the input file first causes an out-of-bounds read to determine whether a block is cached; a null value then causes allocation of a block and an out-of-bounds pointer write to the same element. The invalid read may crash the process, while the write may corrupt heap state and could permit arbitrary code execution. This issue is fixed in versions 1.21.2, 1.22.3, 1.23.2, and 1.24.
Who should check
Teams running samtools or HTSlib at versions up to 1.23.1, 1.22.2 or 1.21.1 that decode experimental CRAM v4 files
“<= 1.23.1, 1.22.2 and 1.21.1”
What to do
Check whether your setup matches what the bug needs.
Decoding CRAM v4 files with the experimental XPACK or XRLE decoders in HTSlibUpgrade to a fixed version: 1.21.2, 1.22.3, 1.23.2.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-62257 (HTSlib: Heap read and write overflow in HTSlib CRAM 4.0 decoder), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-62257 (entry last updated 2026-11-19):
Affected:
- samtools htslib: fixed in 1.21.2; from 1.22.0, fixed in 1.22.3; from 1.23.0, fixed in 1.23.2
Fixed versions: 1.21.2, 1.22.3, 1.23.2.
Conditions (all must be true for the bug to be hit):
- Decoding CRAM v4 files with the experimental XPACK or XRLE decoders in HTSlib (source: https://github.com/samtools/htslib/security/advisories/GHSA-6q7c-m967-9v37)
Setup: the bug needs a feature or setting that is off by default or uncommon. Check whether each asset has it on.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-62257 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-62257 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/samtools/htslib/security/advisories/GHSA-6q7c-m967-9v37
- https://github.com/samtools/htslib/pull/2020
- https://github.com/samtools/htslib/pull/2046
- https://github.com/samtools/htslib/commit/a3e8dca14dcfdc6167281721ede6d6ecd3395bad
- https://github.com/samtools/htslib/commit/c0b50372ed133c650fa0a641607da5cde46bcd8c
- https://github.com/samtools/htslib/commit/d66a77dbf8f52f7f44efd7929a28b94bbfc17f2f
- https://github.com/samtools/htslib/releases/tag/1.21.2
- https://github.com/samtools/htslib/releases/tag/1.22.3
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-62257
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-62257"}.Affected versions
- samtools htslibfixed in 1.21.2; From 1.22.0 · fixed in 1.22.3; From 1.23.0 · fixed in 1.23.2
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure12/25Specific setups only, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.8/10CVSS 8.8
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
Timeline
- CVE published
- First seen by cve.now
Evidence 12
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · samtools/htslib · Advisory GHSA-6q7c-m967-9v37 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-62257 |
| Record | NVD · CVE-2026-62257 |
| Other links 9 | |
| Repository | GitHub · samtools/htslib · Pull request #2020 |
| Repository | GitHub · samtools/htslib · Pull request #2046 |
| Repository | GitHub · samtools/htslib · Commit a3e8dca1 |
| Repository | GitHub · samtools/htslib · Commit c0b50372 |
| Repository | GitHub · samtools/htslib · Commit d66a77db |
| Repository | GitHub · samtools/htslib · Release 1.21.2 |
| Repository | GitHub · samtools/htslib · Release 1.22.3 |
| Repository | GitHub · samtools/htslib · Release 1.23.2 |
| Repository | GitHub · samtools/htslib · Release 1.24 |
Questions about CVE-2026-62257
Is CVE-2026-62257 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
The experimental CRAM v4 XPACK and XRLE decoders cache a copy of a block pointer, which leads to heap read and write out-of-bounds access. The out-of-bounds access may crash the process or possibly allow arbitrary code execution.
Source: github.com
Which versions are affected by CVE-2026-62257?
htslib: before 1.21.2; from 1.22.0 before 1.22.3; from 1.23.0 before 1.23.2.
Source: cve.now feed data
Am I affected, and how do I check?
HTSlib versions before 1.21.2, 1.22.0 through 1.22.2, and 1.23.0 through 1.23.1 are affected, and only when CRAM v4 files are decoded with the experimental XPACK or XRLE decoders. To check, run samtools --version to see the linked HTSlib version and confirm whether CRAM v4 input is being decoded.
Source: github.com
How do I fix CVE-2026-62257?
Upgrade HTSlib to 1.21.2, 1.22.3, or 1.23.2, using the one on the same release line as the version in use.
Source: github.com
Related
- CVE-2026-62258HTSlib: Stack write overflow in HTSlib CRAM decoder
- CVE-2026-63390HTSlib: Heap buffer overflow in BCF reader due to improper validation of input.
- CVE-2026-31968HTSlib CRAM decoder vulnerable to buffer overflow
- CVE-2026-31963HTSlib CRAM reader has heap buffer overflow due to improper validation of input
- CVE-2026-31962HTSlib CRAM reader has heap buffer overflow due to improper validation of input
- CVE-2026-62256HTSlib: Heap write overflow in HTSlib FASTA index handling
No corrections so far. Something wrong on this page? Report an error.