Skip to main content
Menu
CVEs

HTSlib heap buffer overflow in BCF reader

HTSlib 1.21.1 and earlier, 1.22.2, and 1.23.1 are affected when a crafted BCF file is opened. Fixed in 1.21.2, 1.22.3, and 1.23.2.

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

8.8HighCNA
Exploited
No known exploitation
Fix
Fixed in 1.21.2, 1.22.3, 1.23.2
Who is exposed
Not reported

Summary

HTSlib, a library for reading bioinformatics file formats, has a heap buffer overflow in its BCF reader caused by an integer overflow in a record-length check. An attacker can exploit it remotely, without logging in, by supplying a crafted BCF file that, when opened, can crash the process, corrupt data, or potentially allow arbitrary code execution.

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, the BCF reader can experience an integer overflow in a record-length check that verifies whether a record contains enough bytes for the expected number and size of stored items. A crafted BCF record can bypass this check, causing reads beyond the stored data and, in some cases, writes beyond the heap buffer when the reader sets the least significant bit of accessed bytes. Opening such a file can crash the process, corrupt data or heap structures, 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 HTSlib 1.21.1 or earlier, 1.22.2, or 1.23.1, including samtools builds that use them, that open BCF files

“<= 1.21.1, 1.22.2, 1.23.1”

github.com

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-63390 (HTSlib: Heap buffer overflow in BCF reader 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-63390 (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):
- HTSlib versions 1.21.1 and earlier, 1.22.2, and 1.23.1 (the advisory lists these as affected) (source: https://github.com/samtools/htslib/security/advisories/GHSA-2wm6-8hgm-7g92)
- The victim opens a crafted BCF file (source: https://github.com/samtools/htslib/security/advisories/GHSA-2wm6-8hgm-7g92)
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-63390 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-63390 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-2wm6-8hgm-7g92
- https://github.com/samtools/htslib/pull/2047
- https://github.com/samtools/htslib/commit/00a30cdb8db1f5832eb58a799383a462c6b58cb3
- https://github.com/samtools/htslib/commit/2713f39242f4afff5382aad5c1ba02abe12950cd
- https://github.com/samtools/htslib/commit/3a3585dc844f7caad266bbec8d91e45c09c1dcd4
- 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-63390
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-63390"}.

Affected versions

cve.now Index

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

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: partial

  4. Record last updated

Evidence 11

Questions about CVE-2026-63390

Is CVE-2026-63390 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?

A crafted BCF file can trigger a heap buffer overflow in HTSlib's BCF reader because input is not properly validated. The overflow can crash the program, overwrite data and heap structures, and possibly allow arbitrary code execution.

Source: github.com

Which versions are affected by CVE-2026-63390?

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?

The advisory lists HTSlib 1.21.1 and earlier, 1.22.2, and 1.23.1 as affected. The issue arises when a BCF file is opened, so check which HTSlib version your tools are built with, such as the version output of an HTSlib-based tool like htsfile.

Source: github.com

How do I fix CVE-2026-63390?

Upgrade to HTSlib 1.21.2, 1.22.3, or 1.23.2, depending on your release line.

Source: github.com

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