CVE-2026-62291

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 97% 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
Trending — 3 sources updated this weekElevated
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: Elevated riskExposed: 0

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 image sequence with a 2x2 primary plane and a 256x256 auxiliary alpha plane can cause attacker-controlled heap corruption during a normal decode and re-encode workflow. Track_Visual::decode_next_image_sample() calls transfer_channel_from_image_as() without checking that the auxiliary alpha dimensions match the main frame. The resulting inconsistent image reaches heif_track_decode_next_image() and then heif_context_encode_image(). In unc_encoder::encode(), unc_encoder_component_interleave::encode_tile() sizes its buffer with compute_tile_data_size_bytes() using the primary dimensions but copies each component using its actual plane dimensions. The oversized alpha plane is therefore copied beyond the allocation, causing an out-of-bounds write; the inverse size mismatch can also produce an out-of-bounds read. This issue is fixed in version 1.23.1.

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity53% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

August 18, 2026

Last Modified

September 9, 2026

Advisory Details (3)

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

Heap out of bounds write in libheif uncompressed encoder when writing images with mismatched auxiliary alpha dimensions · Advisory · strukturag/libheif · GitHub

https://github.com/strukturag/libheif/security/advisories/GHSA-xpw3-9rhw-482x
github_release Patch Available

v1.23.1

Patch available: strukturag/libheif v1.23.1

https://github.com/strukturag/libheif/releases/tag/v1.23.1
github_commit Patch Available

commit ac5521ad5039 (strukturag/libheif)

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

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibheif1 (1.17.6-1ubuntu4.8) @ noble2026-09-18ubuntu
ubuntulibheif1 (1.21.2-3ubuntu0.5) @ resolute2026-09-18ubuntu

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 rangeFixed inDependents
libheif1.19.8-1 ... 1.21.2-4 (8 versions)1.23.1-1—

Weakness Classification(2)

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

All Vendor Advisories

(2)

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 16× in last 7d / 65× 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-09-18 21:47 UTCEG score recompute
  2. 2026-09-18 21:47 UTCVendor advisory
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-17 21:35 UTCEG score recompute
  5. 2026-09-17 21:35 UTCVendor advisory
  6. 2026-09-16 20:09 UTCEG score recompute
  7. 2026-09-16 20:09 UTCVendor advisory
  8. 2026-09-16 14:08 UTCEPSS rescore
  9. 2026-09-16 05:15 UTCEPSS rescore
  10. 2026-09-15 18:51 UTCEG score recompute
  11. 2026-09-15 18:51 UTCVendor advisory
  12. 2026-09-14 19:27 UTCVendor advisory
  13. 2026-09-13 18:59 UTCEG score recompute
  14. 2026-09-13 18:59 UTCVendor advisory
  15. 2026-09-12 19:53 UTCEG score recompute
  16. 2026-09-12 19:53 UTCVendor advisory
  17. 2026-09-11 20:50 UTCEG score recompute
  18. 2026-09-11 20:50 UTCVendor advisory
  19. 2026-09-11 09:37 UTCEPSS rescore
  20. 2026-09-10 21:40 UTCEG score recompute
  21. 2026-09-10 21:40 UTCVendor advisory
  22. 2026-09-09 22:38 UTCVendor advisory
  23. 2026-09-09 03:14 UTCEG score recompute
  24. 2026-09-09 03:14 UTCVendor advisory
  25. 2026-09-08 22:01 UTCEPSS rescore
Show 45 more
  1. 2026-09-08 04:11 UTCEG score recompute
  2. 2026-09-08 04:11 UTCVendor advisory
  3. 2026-09-07 16:01 UTCEPSS rescore
  4. 2026-09-07 05:08 UTCEG score recompute
  5. 2026-09-07 05:08 UTCVendor advisory
  6. 2026-09-06 13:47 UTCEPSS rescore
  7. 2026-09-06 06:02 UTCEG score recompute
  8. 2026-09-06 06:02 UTCVendor advisory
  9. 2026-09-05 07:00 UTCEG score recompute
  10. 2026-09-05 07:00 UTCVendor advisory
  11. 2026-09-04 07:57 UTCEG score recompute
  12. 2026-09-04 05:07 UTCEPSS rescore
  13. 2026-09-03 08:54 UTCEG score recompute
  14. 2026-09-02 14:12 UTCEPSS rescore
  15. 2026-09-02 09:51 UTCEG score recompute
  16. 2026-09-01 13:54 UTCEPSS rescore
  17. 2026-09-01 10:47 UTCEG score recompute
  18. 2026-09-01 04:40 UTCEPSS rescore
  19. 2026-08-31 11:43 UTCEG score recompute
  20. 2026-08-31 11:43 UTCVendor advisory
  21. 2026-08-30 19:17 UTCEPSS rescore
  22. 2026-08-30 12:40 UTCEG score recompute
  23. 2026-08-30 12:40 UTCVendor advisory
  24. 2026-08-30 01:22 UTCEPSS rescore
  25. 2026-08-29 13:32 UTCEG score recompute
  26. 2026-08-29 13:32 UTCVendor advisory
  27. 2026-08-28 21:42 UTCEPSS rescore
  28. 2026-08-28 13:53 UTCVendor advisory
  29. 2026-08-27 14:44 UTCEG score recompute
  30. 2026-08-27 14:25 UTCEPSS rescore
  31. 2026-08-26 15:41 UTCEG score recompute
  32. 2026-08-26 14:46 UTCEPSS rescore
  33. 2026-08-25 16:36 UTCEG score recompute
  34. 2026-08-25 13:49 UTCEPSS rescore
  35. 2026-08-24 17:30 UTCEG score recompute
  36. 2026-08-22 19:26 UTCEG score recompute
  37. 2026-08-21 23:49 UTCEPSS rescore
  38. 2026-08-21 20:23 UTCEG score recompute
  39. 2026-08-21 19:20 UTCEG score recompute
  40. 2026-08-20 22:55 UTCEPSS rescore
  41. 2026-08-19 21:27 UTCEG score recompute
  42. 2026-08-19 17:04 UTCEPSS rescore
  43. 2026-08-18 22:23 UTCEG score recompute
  44. 2026-08-18 21:23 UTCEG score recompute
  45. 2026-08-18 21:23 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-62291?
CVE-2026-62291 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 image sequence with a 2x2 primary plane and a 256x256 auxiliary alpha plane can cause attacker-controlled heap corruption during a normal decode and re-encode workflow. TrackVisual::decodenextimagesample()…
When was CVE-2026-62291 disclosed?
CVE-2026-62291 was first published in the National Vulnerability Database 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-62291 actively exploited?
CVE-2026-62291 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 97.0% of all scored CVEs.
What is the CVSS score of CVE-2026-62291?
CVE-2026-62291 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-62291?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-62291, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-62291

Explore →

Is Your Infrastructure Affected by CVE-2026-62291?

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

Start Free Scan →Browse All CVEs