CVE-2026-62258

HIGHPre-NVD 8.88.8
EchelonGraph scoreLOW confidence

This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.8% (58th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: a secondary CVSS source

Also known asEUVD-2026-130306 (ENISA EUVD)Source: ENISA EUVD

8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS
8.8
EG Score
8.8HIGHlow confidence
EG Risk
55
EG Risk 55/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0% × 40%
No KEV listing, EG-KEV tier or EPSS when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.8%
EPSS %ILE
58th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.8% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 19, 2026

Last Modified

November 19, 2026

Advisory Details (9)

Auto-updated Nov 19, 2026
Patch available. Sources: github, github_commit, github_pr, github_release.
GitHub release Patch Available

1.24

Patch available: samtools/htslib 1.24

https://github.com/samtools/htslib/releases/tag/1.24
GitHub release Patch Available

1.23.2

Patch available: samtools/htslib 1.23.2

https://github.com/samtools/htslib/releases/tag/1.23.2
GitHub release Patch Available

1.22.3

Patch available: samtools/htslib 1.22.3

https://github.com/samtools/htslib/releases/tag/1.22.3
GitHub release Patch Available

1.21.2

Patch available: samtools/htslib 1.21.2

https://github.com/samtools/htslib/releases/tag/1.21.2
GitHub commit Patch Available

commit f1d1bf835aaa (samtools/htslib)

Patch available: samtools/htslib 1.21.2 (contains commit f1d1bf835aaa)

https://github.com/samtools/htslib/commit/f1d1bf835aaafa1e511996dcd49760c36f683b17
GitHub commit Patch Available

commit df93e245f1b5 (samtools/htslib)

Patch available: samtools/htslib 1.22.3 (contains commit df93e245f1b5)

https://github.com/samtools/htslib/commit/df93e245f1b517aec86c69684fcb2faf5942c5c2
GitHub commit Patch Available

commit 25278797c251 (samtools/htslib)

Patch available: samtools/htslib 1.23.2 (contains commit 25278797c251)

https://github.com/samtools/htslib/commit/25278797c251a9af789382ecf5aa0c86f417bdf5
GitHub pull request Patch Available

CRAM bug fixes

Patch available: samtools/htslib 1.24 (PR #2046 merged 2026-07-09)

https://github.com/samtools/htslib/pull/2046
GitHub advisoryMentions a patch (unverified)

Stack write overflow in HTSlib CRAM decoder · Advisory · samtools/htslib · GitHub

https://github.com/samtools/htslib/security/advisories/GHSA-2jx2-wm7f-rv9m

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 5× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-21 17:26 UTCOSV refresh
  2. 2026-11-21 16:40 UTCEPSS rescoreEPSS 0.8% · 58th percentile
  3. 2026-11-20 16:37 UTCEPSS rescoreEPSS 0.8% · 58th percentile
  4. 2026-11-20 01:36 UTCEchelonGraph re-scored
  5. 2026-11-19 17:03 UTCENISA EUVD ID recordedEUVD-2026-130306 · Source: ENISA EUVD
  6. 2026-11-19 16:31 UTCEchelonGraph re-scored
  7. 2026-11-19 15:59 UTCEchelonGraph re-scoredFirst assessed: 8.8 HIGH
  8. 2026-11-19 15:58 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-62258?
CVE-2026-62258 is a high-severity vulnerability; its CVE record was published on November 19, 2026. 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…
When was the CVE record for CVE-2026-62258 published?
The CVE record for CVE-2026-62258 was published on November 19, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 19, 2026; the record at its source may have been updated since.
Is CVE-2026-62258 actively exploited?
CVE-2026-62258 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (58th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-62258?
CVE-2026-62258 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-62258?
A fix for CVE-2026-62258 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-62258

Explore →

Is Your Infrastructure Affected by CVE-2026-62258?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.