CVE-2026-62377

MEDIUMPre-NVD 4.34.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 75% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
4.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

libheif is a HEIF and AVIF file format decoder and encoder. In 1.23.0 and earlier, a crafted HEIF sequence accepted by heif_context_read_from_memory() can leave the context with no registered sequence tracks and crash when heif_context_get_track(ctx, 0) is called. HeifContext::get_track() in libheif/context.cc executes assert(has_sequence()) before its normal error handling, so assert-enabled builds abort instead of allowing the public wrapper in libheif/api/libheif/heif_sequences.cc to return null. In release builds, removing the assertion lets the track_id zero path dereference m_tracks.begin()->second on an empty map, which is undefined behavior and typically crashes. The issue is reachable through documented public APIs after parsing attacker-controlled bytes. This issue is fixed in version 1.23.1.

CVSS v3
4.3
EG Score
4.3(medium)
EG Risk
19(Track)
EG Risk 19/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity43% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
25%
KEV
Not listed

Published

August 18, 2026

Last Modified

August 19, 2026

Advisory Details (4)

Auto-updated Aug 18, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_release, github.
github Patch Available🟡 PoC Available

Reachable assertion in HeifContext::get_track() aborts on a valid-but-empty HEIF sequence file (context.cc:2110) · Advisory · strukturag/libheif · GitHub

https://github.com/strukturag/libheif/security/advisories/GHSA-9ww4-9v47-m7pj
github_release Patch Available

v1.23.1

Patch available: strukturag/libheif v1.23.1

https://github.com/strukturag/libheif/releases/tag/v1.23.1
generic

Reachable assertion in `HeifContext::get_track()` aborts on a valid-but-empty HEIF sequence file (`context.cc:2110`) · Issue #1844 · strukturag/libheif · GitHub

https://github.com/strukturag/libheif/issues/1844
github_commit Patch Available

commit e1a0bc1c1ae7 (strukturag/libheif)

Patch available: strukturag/libheif v1.23.1 (contains commit e1a0bc1c1ae7)

https://github.com/strukturag/libheif/commit/e1a0bc1c1ae74f8075eaca30a1cdb2b9bee698d3

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 16× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-26 14:46 UTCEPSS rescore
  2. 2026-08-25 19:18 UTCEG score recompute
  3. 2026-08-25 13:49 UTCEPSS rescore
  4. 2026-08-24 19:18 UTCEG score recompute
  5. 2026-08-23 19:18 UTCEG score recompute
  6. 2026-08-23 00:19 UTCEPSS rescore
  7. 2026-08-22 19:19 UTCEG score recompute
  8. 2026-08-21 23:49 UTCEPSS rescore
  9. 2026-08-21 19:19 UTCEG score recompute
  10. 2026-08-20 22:55 UTCEPSS rescore
  11. 2026-08-19 19:20 UTCEG score recompute
  12. 2026-08-19 18:23 UTCEG score recompute
  13. 2026-08-19 17:04 UTCEPSS rescore
  14. 2026-08-18 22:23 UTCEG score recompute
  15. 2026-08-18 21:23 UTCEG score recompute
  16. 2026-08-18 21:23 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-62377?
CVE-2026-62377 is a medium vulnerability published on August 18, 2026. libheif is a HEIF and AVIF file format decoder and encoder. In 1.23.0 and earlier, a crafted HEIF sequence accepted by heifcontextreadfrommemory() can leave the context with no registered sequence tracks and crash when heifcontextgettrack(ctx, 0) is called. HeifContext::gettrack() in…
When was CVE-2026-62377 disclosed?
CVE-2026-62377 was first published in the National Vulnerability Database on August 18, 2026, with the most recent update on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-62377 actively exploited?
CVE-2026-62377 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 75.1% of all scored CVEs.
What is the CVSS score of CVE-2026-62377?
CVE-2026-62377 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2026-62377?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-62377, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-62377?

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

Start Free Scan →Browse All CVEs