cve.bz

CVE-2026-62258 HTSlib: Stack write overflow in HTSlib CRAM decoder

8.8 highEPSS 0.8%

High (8.8) in samtools htslib. EPSS 0.8% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 4.0

8.8 high
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N
EPSS
0.8% estimated probability of exploitation activity in the next 30 days; 58th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-11-19. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-121 Stack-based Buffer Overflow
CWE-787 Out-of-bounds Write
Published
Modified
Assigned by
GitHub_M (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-62258 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-62258?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-62258?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-62258 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
samtools htslib< 1.21.2
samtools htslib>= 1.22.0, < 1.22.3
samtools htslib>= 1.23.0, < 1.23.2

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13htslibno fix listedDEBIAN-CVE-2026-62258
Debian14htslib1.24-2DEBIAN-CVE-2026-62258

From the distributions' data via OSV.dev: the Debian Security Tracker. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian.

References

Check your stackJSON