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.4% (33rd percentile of EPSS-scored CVEs). 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
Trending — 3 sources updated this week
4.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 4.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.3MEDIUMmedium confidence
EG Risk
20
EG Risk 20/100CISA SSVC

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%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
33rd
KEV
Not listed

CISA SSVCTrack at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 18, 2026

Last Modified

September 9, 2026

Advisory Details (4)

Auto-updated Aug 18, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_release, github.
githubMentions a patch (unverified)🟡 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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibheif1 (1.21.2-3ubuntu0.5) @ resolute2026-10-07ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
libheif1.19.8-1 ... 1.21.2-4 (8 versions)
  • every version up to 1.23.1-1: fixed in 1.23.1-1
—

Weakness Classification(2)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 13× in last 7d / 62× 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.

Showing the most recent 100 of 102 total refreshes for this CVE.

  1. 2026-10-10 20:00 UTCEPSS rescore
  2. 2026-10-09 20:07 UTCEPSS rescore
  3. 2026-10-08 17:13 UTCEPSS rescore
  4. 2026-10-08 09:00 UTCEG score recompute
  5. 2026-10-07 23:48 UTCEPSS rescore
  6. 2026-10-07 08:04 UTCEG score recompute
  7. 2026-10-07 08:04 UTCVendor advisory
  8. 2026-10-06 15:18 UTCEPSS rescore
  9. 2026-10-06 08:03 UTCEG score recompute
  10. 2026-10-06 08:03 UTCVendor advisory
  11. 2026-10-05 17:43 UTCEPSS rescore
  12. 2026-10-04 23:22 UTCEPSS rescore
  13. 2026-10-04 21:28 UTCVendor advisory
  14. 2026-10-03 17:01 UTCEG score recompute
  15. 2026-10-03 17:01 UTCVendor advisory
  16. 2026-10-03 14:26 UTCEPSS rescore
  17. 2026-10-02 17:56 UTCEPSS rescore
  18. 2026-10-02 09:13 UTCEG score recompute
  19. 2026-10-02 09:13 UTCVendor advisory
  20. 2026-10-01 19:50 UTCEPSS rescore
  21. 2026-10-01 08:54 UTCEG score recompute
  22. 2026-10-01 08:54 UTCVendor advisory
  23. 2026-09-30 15:03 UTCEPSS rescore
  24. 2026-09-30 08:54 UTCEG score recompute
  25. 2026-09-30 08:54 UTCVendor advisory
Show 75 more
  1. 2026-09-29 07:18 UTCEG score recompute
  2. 2026-09-29 07:18 UTCVendor advisory
  3. 2026-09-28 13:51 UTCEPSS rescore
  4. 2026-09-28 07:18 UTCEG score recompute
  5. 2026-09-28 07:18 UTCVendor advisory
  6. 2026-09-27 07:18 UTCEG score recompute
  7. 2026-09-27 07:18 UTCVendor advisory
  8. 2026-09-26 15:59 UTCEPSS rescore
  9. 2026-09-25 00:58 UTCEG score recompute
  10. 2026-09-25 00:58 UTCVendor advisory
  11. 2026-09-24 00:12 UTCEG score recompute
  12. 2026-09-24 00:12 UTCVendor advisory
  13. 2026-09-23 17:54 UTCEPSS rescore
  14. 2026-09-23 00:13 UTCEG score recompute
  15. 2026-09-23 00:13 UTCVendor advisory
  16. 2026-09-22 00:13 UTCEG score recompute
  17. 2026-09-22 00:13 UTCVendor advisory
  18. 2026-09-21 00:12 UTCEG score recompute
  19. 2026-09-21 00:12 UTCVendor advisory
  20. 2026-09-20 20:16 UTCEPSS rescore
  21. 2026-09-20 00:12 UTCEG score recompute
  22. 2026-09-20 00:12 UTCVendor advisory
  23. 2026-09-19 00:11 UTCEG score recompute
  24. 2026-09-19 00:11 UTCVendor advisory
  25. 2026-09-18 19:28 UTCEPSS rescore
  26. 2026-09-18 00:12 UTCEG score recompute
  27. 2026-09-18 00:12 UTCVendor advisory
  28. 2026-09-16 23:57 UTCEG score recompute
  29. 2026-09-16 23:57 UTCVendor advisory
  30. 2026-09-16 14:08 UTCEPSS rescore
  31. 2026-09-16 05:15 UTCEPSS rescore
  32. 2026-09-15 23:57 UTCEG score recompute
  33. 2026-09-13 23:36 UTCEG score recompute
  34. 2026-09-12 23:37 UTCEG score recompute
  35. 2026-09-11 23:37 UTCEG score recompute
  36. 2026-09-11 14:53 UTCEPSS rescore
  37. 2026-09-11 09:37 UTCEPSS rescore
  38. 2026-09-10 22:37 UTCEG score recompute
  39. 2026-09-09 03:04 UTCEG score recompute
  40. 2026-09-08 22:01 UTCEPSS rescore
  41. 2026-09-08 03:05 UTCEG score recompute
  42. 2026-09-07 16:01 UTCEPSS rescore
  43. 2026-09-07 03:05 UTCEG score recompute
  44. 2026-09-06 13:47 UTCEPSS rescore
  45. 2026-09-06 02:53 UTCEG score recompute
  46. 2026-09-05 02:53 UTCEG score recompute
  47. 2026-09-04 05:07 UTCEPSS rescore
  48. 2026-09-03 02:45 UTCEG score recompute
  49. 2026-09-02 14:12 UTCEPSS rescore
  50. 2026-09-02 02:45 UTCEG score recompute
  51. 2026-09-01 13:54 UTCEPSS rescore
  52. 2026-09-01 04:40 UTCEPSS rescore
  53. 2026-08-31 02:42 UTCEG score recompute
  54. 2026-08-30 19:17 UTCEPSS rescore
  55. 2026-08-30 02:43 UTCEG score recompute
  56. 2026-08-30 01:22 UTCEPSS rescore
  57. 2026-08-29 02:43 UTCEG score recompute
  58. 2026-08-28 21:42 UTCEPSS rescore
  59. 2026-08-27 19:17 UTCEG score recompute
  60. 2026-08-27 14:25 UTCEPSS rescore
  61. 2026-08-26 19:17 UTCEG score recompute
  62. 2026-08-26 14:46 UTCEPSS rescore
  63. 2026-08-25 19:18 UTCEG score recompute
  64. 2026-08-25 13:49 UTCEPSS rescore
  65. 2026-08-24 19:18 UTCEG score recompute
  66. 2026-08-23 19:18 UTCEG score recompute
  67. 2026-08-23 00:19 UTCEPSS rescore
  68. 2026-08-22 19:19 UTCEG score recompute
  69. 2026-08-21 23:49 UTCEPSS rescore
  70. 2026-08-21 19:19 UTCEG score recompute
  71. 2026-08-20 22:55 UTCEPSS rescore
  72. 2026-08-19 19:20 UTCEG score recompute
  73. 2026-08-19 18:23 UTCEG score recompute
  74. 2026-08-19 17:04 UTCEPSS rescore
  75. 2026-08-18 22:23 UTCEG score recompute

Related CVEs(same product + same vendor + same CWE)

Same vendor

1 shown

ubuntu:USN-8774-1

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 on August 18, 2026, with the most recent update on September 9, 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.4% probability of exploitation in the next 30 days (33rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-62377?
CVE-2026-62377 has a CVSS base score of 4.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-62377?
A fix for CVE-2026-62377 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by 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.

Book a Demo →Browse All CVEs