CVE-2026-47709

What it is

libheif is a HEIF and AVIF file format decoder and encoder. Versions prior to 1.22.0 crashes in the public C API `heif_image_handle_get_image_tiling()` when a malformed uncompressed HEIF image item has an associated `uncC` property but no associated `ispe` property. In debug builds this trips the `ispe && uncC` assertion in `ImageItem_uncompressed::get_heif_image_tiling()`. In a release/NDEBUG ASan build, the same file causes a null pointer read at address `0xa8`. Version 1.22.0 fixes the issue.

At a glance

Exploitability

Can be exploited locally on the machine without logging in. High risk of service disruption.

Exploit odds

0.2% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-07-21 22:17 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-10-24 19:10 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.2% in the next 30 days (EPSS).
• Severity: 6.9 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2026-07-21 22:17 UTC

Last modified

2026-10-24 19:10 UTC

Exploit probability

0.2% · EPSS, next 30 days

Weakness

CWE-476 · NULL pointer dereference

Record status

Analyzed

Affected

• Struktur Libheif < 1.22.0

Attack profile CVSS 4.0 · 6.9

Attack vector

Local

Complexity

Low

Attack requirements

None

Privileges needed

None

User interaction

None

Confidentiality

None

Integrity

None

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2026-47709.md and follow it. Check whether this project is affected by CVE-2026-47709. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge