HTSlib out-of-bounds read in CRAM BETA and XPACK decoders
- Exploited
- No known exploitation
- Fix
- Fixed in 1.21.2, 1.22.3, 1.23.2
- Who is exposed
- Not reported
Summary
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 CRAM BETA decoder functions cram_beta_decode_long, cram_beta_decode_int, and cram_beta_decode_char, and the experimental CRAM v4 XPACK functions cram_xpack_decode_long and cram_xpack_decode_int, have bounds-checking flaws caused by integer overflow after a multiplication. The resulting incorrect bounds check can allow decoding to read beyond the supplied input buffer, potentially leaking process-state information or crashing the process. This issue is fixed in versions 1.21.2, 1.22.3, 1.23.2, and 1.24.
What to do
Upgrade 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-62260 (HTSlib: Out-of-bounds read in HTSlib CRAM 3.x and 4.0 readers due to improper validation of input), 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-62260 (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.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-62260 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-62260 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-rjqv-xg3q-g423
- https://github.com/samtools/htslib/pull/2046
- https://github.com/samtools/htslib/commit/3eb519cd8a9be35275db46a439eb158e70fe4151
- https://github.com/samtools/htslib/commit/3eef4aece30bc008b251e377085fc944d008d06a
- https://github.com/samtools/htslib/commit/a3e8dca14dcfdc6167281721ede6d6ecd3395bad
- https://github.com/samtools/htslib/releases/tag/1.21.2
- https://github.com/samtools/htslib/releases/tag/1.22.3
- https://github.com/samtools/htslib/releases/tag/1.23.2
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-62260
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-62260"}.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
- Exploitation0/40No signal
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.9/10CVSS 6.9
- 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
- Would score about 29 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Evidence 11
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · samtools/htslib · Advisory GHSA-rjqv-xg3q-g423 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-62260 |
| Record | NVD · CVE-2026-62260 |
| Other links 8 | |
| Repository | GitHub · samtools/htslib · Pull request #2046 |
| Repository | GitHub · samtools/htslib · Commit 3eb519cd |
| Repository | GitHub · samtools/htslib · Commit 3eef4aec |
| Repository | GitHub · samtools/htslib · Commit a3e8dca1 |
| 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-62260
Is CVE-2026-62260 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
Which versions are affected by CVE-2026-62260?
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
How do I fix CVE-2026-62260?
Upgrade to a fixed version: 1.21.2, 1.22.3, 1.23.2.
Source: cve.now feed data
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.