Skip to main content
Menu
CVEs

HTSlib heap buffer overflow in FASTA index retrieval

Affects HTSlib 1.23.1 and earlier, 1.22.2 and earlier, and 1.21.1 and earlier when reading FASTA .fai indexes whose recorded line width is off by one from the bases per line. Fixed in 1.21.2, 1.22.3, and 1.23.2.

CVE-2026-62256Published November 19, 2026, updated

7.1HighCNA
Exploited
No known exploitation
Fix
Fixed in 1.21.2, 1.22.3, 1.23.2
Who is exposed
Specific setups only

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, fai_retrieve does not verify that the line width recorded in a FASTA .fai index is greater than or equal to the number of bases per line. When the line width is exactly one less than the base count, retrieval allocates an undersized heap buffer and writes one byte beyond its end; larger discrepancies instead cause an allocation failure that is handled. This issue can corrupt heap memory and crash the process. 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 older than the fixed releases that read FASTA .fai indexes via fai_retrieve, such as samtools faidx users.

“<= 1.23.1, 1.22.2 and 1.21.1”

github.com

What to do

  1. Check whether your setup matches what the bug needs.

    Affected HTSlib versions: 1.23.1 and earlier, 1.22.2 and earlier, and 1.21.1 and earlier. A FASTA .fai index whose recorded line width differs from the bases per line, read through fai_retrieve; the overflow occurs when the width is one less than the base count.
  2. 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-62256 (HTSlib: Heap write overflow in HTSlib FASTA 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-62256 (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 earlier, and 1.21.1 and earlier. (source: https://github.com/samtools/htslib/security/advisories/GHSA-4hjq-r829-8c8v)
- A FASTA .fai index whose recorded line width differs from the bases per line, read through fai_retrieve; the overflow occurs when the width is one less than the base count. (source: https://github.com/samtools/htslib/security/advisories/GHSA-4hjq-r829-8c8v)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, a user action.
CISA KEV: CVE-2026-62256 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-62256 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-4hjq-r829-8c8v
- https://github.com/samtools/htslib/pull/2008
- https://github.com/samtools/htslib/commit/4af640f9ffd7f1fac95a739df7f560e3e5557960
- https://github.com/samtools/htslib/commit/504fb841b70afb948f58089c3a4337ce875c1e52
- https://github.com/samtools/htslib/commit/567fd43c6ef938de53c98217f99336e3ce5a60ab
- https://github.com/samtools/htslib/commit/cdf22929aad8dde719c1b2070ad565ac9dd76c02
- 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-62256
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-62256"}.

Affected versions

cve.now Index

19Pof 100 · provisional · methodology v3
  • 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
  • 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

  1. CVE published
  2. First seen by cve.now

Evidence 12

Questions about CVE-2026-62256

Is CVE-2026-62256 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 fai_retrieve function does not check that the line length recorded in a FASTA .fai index is consistent with the number of bases per line. When the recorded width is one less than the base count, it writes past the end of a heap buffer.

Source: github.com

Which versions are affected by CVE-2026-62256?

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 earlier, and 1.21.1 and earlier are affected. The issue applies to code that reads FASTA .fai index files through fai_retrieve, so check the installed HTSlib version and whether a program using it reads such indexes.

Source: github.com

How do I fix CVE-2026-62256?

Upgrade to HTSlib 1.21.2 on the 1.21 branch, 1.22.3 on the 1.22 branch, or 1.23.2 on the 1.23 branch.

Source: github.com

No corrections so far. Something wrong on this page? Report an error.