CVE-2026-62291

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (8th 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: EPSS, a secondary CVSS source
Elevated

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

5.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.3Exploit: No code on recordExposed 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 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.3MEDIUMmedium confidence
EG Risk
40
EG Risk 40/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)
Severity53% × 45%
Impact severity (EG Severity): CVSS 5.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (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.
EPSS PROB
0.2%
EPSS %ILE
8th
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 (5.3): severity, escalated by confirmed exploitation. This CVE's 5.3 is its impact severity (EG Severity), not escalated.

EG Severity
5.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). 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; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade 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; Track* at high (mission-essential systems).

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

Exploitation public PoC (CISA Vulnrichment) · Automatable no (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (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

August 18, 2026

Last Modified

October 22, 2026

Advisory Details (3)

Auto-updated Aug 18, 2026
Patch available. Sources: github_commit, github_release, github.
GitHub advisoryMentions a patch (unverified)

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 / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibheif1 (1.12.0-2ubuntu0.1~esm4) @ jammy2026-10-22ubuntu
ubuntulibheif1 (1.21.2-3ubuntu0.5) @ resolute2026-10-22ubuntu

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

(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 7× in last 7d / 47× 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 it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 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). Most recent first.

Showing the most recent 100 of 149 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 49 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

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

Same vendor

2 shown

ubuntu:USN-8774-1 · ubuntu:USN-8683-1

Frequently asked(5)

What is CVE-2026-62291?
CVE-2026-62291 is a medium-severity vulnerability; its CVE record was 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.…
When was the CVE record for CVE-2026-62291 published?
The CVE record for CVE-2026-62291 was published on August 18, 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 October 22, 2026; the record at its source may have been updated since.
Is CVE-2026-62291 actively exploited?
CVE-2026-62291 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (8th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-62291?
CVE-2026-62291 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-62291?
A fix for CVE-2026-62291 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-62291

Explore →

Is Your Infrastructure Affected by CVE-2026-62291?

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

Book a Demo →Browse All CVEs