CVE-2026-62292
libheif tile-decoding integer wrap allows OOB read and crash; patched in 1.23.1
Is CVE-2026-62292 being exploited?
Not confirmed. CVE-2026-62292 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.45% probability of exploitation in the next 30 days.
How severe is CVE-2026-62292?
CVE-2026-62292 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-62292?
Yes. A fix has been recorded for CVE-2026-62292. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-62292 affect?
CVE-2026-62292 affects libheif 1.19.0–1.23.0, applications linking libheif (image viewers, editors, OS decoders). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-62292?
Upgrade libheif to >= 1.23.1 and update dependent apps
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Crafted HEIF/AVIF tile triggers integer wrap leading to out-of-bounds read and process crash during decode; may enable memory corruption and possible RCE.
Patch when possible
- affected>= 1.19.0 and < 1.23.1
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.