HTSlib heap write overflow in CRAM index handling
Affects HTSlib 1.23.1 or earlier, 1.22.2 or earlier, and 1.21.1 or earlier when a malformed CRAI index file is loaded for a CRAM file. Fixed in 1.21.2, 1.22.3, and 1.23.2.
- Exploited
- Proof of concept public, per CISA
- 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 write overflow in its CRAM index handling. A remote attacker without a login can trigger it by supplying a malformed .crai index file, but a user must perform a region query for the flaw to fire, which can cause denial of service or memory corruption.
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, cram_index_load does not verify that the number of reference sequences in a CRAM .crai index does not exceed the CRAM header reference count. A malformed index can drive unbounded index-array allocation, and when the number of references in the index is within two of INT_MAX, the growth calculation can wrap, read beyond a heap buffer, and use the resulting value as a pointer for an unchecked memory write. Any region query can trigger the flaw, causing denial of service or memory corruption. This issue is fixed in versions 1.21.2, 1.22.3, 1.23.2, and 1.24.
Who should check
Teams running HTSlib 1.23.1 or earlier, 1.22.2 or earlier, or 1.21.1 or earlier that open CRAM files with .crai indexes for region queries, such as samtools view or pysam fetch() users
“<= 1.23.1, 1.22.2 and 1.21.1”
What to do
Check whether your setup matches what the bug needs.
Running HTSlib 1.23.1 or earlier, 1.22.2 or earlier, or 1.21.1 or earlier A malformed CRAI index file is loaded for the CRAM file Any region query on the CRAM file triggers the flaw, including valid queriesUpgrade 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-62255 (HTSlib: Heap write overflow in HTSlib CRAM index handling), 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-62255 (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):
- Running HTSlib 1.23.1 or earlier, 1.22.2 or earlier, or 1.21.1 or earlier (source: https://github.com/samtools/htslib/security/advisories/GHSA-28r7-prwc-hf5c)
- A malformed CRAI index file is loaded for the CRAM file (source: https://github.com/samtools/htslib/security/advisories/GHSA-28r7-prwc-hf5c)
- Any region query on the CRAM file triggers the flaw, including valid queries (source: https://github.com/samtools/htslib/security/advisories/GHSA-28r7-prwc-hf5c)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, no login, a user action.
CISA KEV: CVE-2026-62255 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-62255 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-28r7-prwc-hf5c
- https://github.com/samtools/htslib/pull/2029
- https://github.com/samtools/htslib/commit/08fbbceefdfac073e768c1fce593181ca7379222
- https://github.com/samtools/htslib/commit/57e1a0763c9a5f34a1d1ab9deb3a3ad2bd8fe11d
- https://github.com/samtools/htslib/commit/8a2394e63c9bdd758cc6a7de04c5e2ee7acc8e65
- https://github.com/samtools/htslib/commit/924e21755d0b5db7a33f1920d20c0e441667d22f
- 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-62255
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-62255"}.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
- Exploitation15/40CISA rates a proof of concept as public
- Exposure12/25Specific setups only, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 69 if added to CISA KEV
- Would score about 64 if CISA's SSVC rates exploitation active
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: partial
- Record last updated
Evidence 12
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · samtools/htslib · Advisory GHSA-28r7-prwc-hf5c |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-62255 |
| Record | NVD · CVE-2026-62255 |
| Other links 9 | |
| Repository | GitHub · samtools/htslib · Pull request #2029 |
| Repository | GitHub · samtools/htslib · Commit 08fbbcee |
| Repository | GitHub · samtools/htslib · Commit 57e1a076 |
| Repository | GitHub · samtools/htslib · Commit 8a2394e6 |
| Repository | GitHub · samtools/htslib · Commit 924e2175 |
| 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-62255
Is CVE-2026-62255 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. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
A heap write overflow in HTSlib's CRAM index handling. A malformed CRAI index can cause unbounded memory allocation, leading to denial of service, and a memory write through an unvalidated pointer read from heap data, which can corrupt memory. Any region query on the affected CRAM file triggers it, including valid queries.
Source: github.com
Which versions are affected by CVE-2026-62255?
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?
Versions 1.21.1 or earlier, 1.22.2 or earlier, and 1.23.1 or earlier are affected, and only when a malformed CRAI index file is loaded for a CRAM file and a region query is run. To check, look at which HTSlib version your tools are built against and whether a CRAI index file is in use.
Source: github.com
How do I fix CVE-2026-62255?
Upgrade to HTSlib 1.21.2, 1.22.3, or 1.23.2, using the fixed version on your release line.
Source: github.com
Related
- CVE-2026-62258HTSlib: Stack write overflow in HTSlib CRAM decoder
- CVE-2026-62257HTSlib: Heap read and write overflow in HTSlib CRAM 4.0 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
No corrections so far. Something wrong on this page? Report an error.