HTSlib stack buffer overflow in CRAM decoder
Affects HTSlib 1.23.1 and earlier, 1.22.2, and 1.21.1, for all CRAM format versions. No vendor severity is given beyond the CVSS score of 8.8. 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
- Not reported
Summary
Written by a model
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 decoder validates the 254-character query-name limit only after decoding the name into a 1024-byte stack array. An attacker-controlled CRAM record can provide an overlong query name and overflow the local stack buffer before the later validation runs; all CRAM format versions are affected. Opening such a file can crash the process, corrupt stack data, and may 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 1.23.1 and earlier, 1.22.2, or 1.21.1 that open CRAM files from untrusted sources
“<= 1.23.1, 1.22.2 and 1.21.1”
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-62258 (HTSlib: Stack write overflow in HTSlib CRAM 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-62258 (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):
- Affected HTSlib versions: 1.23.1 and earlier, 1.22.2, and 1.21.1 (source: https://github.com/samtools/htslib/security/advisories/GHSA-2jx2-wm7f-rv9m)
- Applies to all CRAM format versions (source: https://github.com/samtools/htslib/security/advisories/GHSA-2jx2-wm7f-rv9m)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-62258 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-62258 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-2jx2-wm7f-rv9m
- https://github.com/samtools/htslib/pull/2046
- https://github.com/samtools/htslib/commit/25278797c251a9af789382ecf5aa0c86f417bdf5
- https://github.com/samtools/htslib/commit/df93e245f1b517aec86c69684fcb2faf5942c5c2
- https://github.com/samtools/htslib/commit/f1d1bf835aaafa1e511996dcd49760c36f683b17
- 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-62258
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-62258"}.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
- Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
- 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 74 if added to CISA KEV
- Would score about 69 if CISA's SSVC rates exploitation active
- Would score about 34 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Evidence 11
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · samtools/htslib · Advisory GHSA-2jx2-wm7f-rv9m |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-62258 |
| Record | NVD · CVE-2026-62258 |
| Other links 8 | |
| Repository | GitHub · samtools/htslib · Pull request #2046 |
| Repository | GitHub · samtools/htslib · Commit 25278797 |
| Repository | GitHub · samtools/htslib · Commit df93e245 |
| Repository | GitHub · samtools/htslib · Commit f1d1bf83 |
| 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-62258
Is CVE-2026-62258 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 CRAM decoder in HTSlib can write past the end of a stack buffer. This can crash the program, overwrite data in unexpected ways, and may allow arbitrary code execution.
Source: github.com
Which versions are affected by CVE-2026-62258?
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 1.23.1 and earlier, 1.22.2, and 1.21.1 are affected, and the flaw applies to all CRAM format versions. To check a version, run samtools --version, which reports the HTSlib version it was built with.
Source: github.com
How do I fix CVE-2026-62258?
Upgrade to HTSlib 1.21.2 on the 1.21 line, 1.22.3 on the 1.22 line, or 1.23.2 on the 1.23 line.
Source: github.com
Related
- 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
- CVE-2026-62256HTSlib: Heap write overflow in HTSlib FASTA index handling
No corrections so far. Something wrong on this page? Report an error.