cve.bz

CVE-2026-32740 struktur libheif: Out-of-bounds Write

8.8 highExploit referenceEPSS 0.7%

High (8.8) in struktur libheif. EPSS 0.7% estimated probability of exploitation activity in the next 30 days.

On this page
libheif is a HEIF and AVIF file format decoder and encoder. Versions 1.21.2 and prior contain a heap-buffer-overflow (write) vulnerability in the grid tile compositing, allowing an attacker to write 64 bytes of fully attacker-controlled data past the end of a chroma plane heap allocation by crafting a HEIF/AVIF file with a 1×4 grid of odd-height tiles. The overflow is triggered during normal image decoding with default build configuration. The written bytes are chroma (Cb/Cr) pixel values from the attacking tile, giving the attacker full control over the overflow content. This issue has been fixed in version 1.22.0.

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS
0.7% (unchanged from 0.7% a week ago; 0.8% 30 days ago) estimated probability of exploitation activity in the next 30 days; 54th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-05-21. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-787 Out-of-bounds Write
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-32740 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-32740?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-32740?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-32740 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
struktur:libheifbefore 1.22.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12libheifno fix listedDEBIAN-CVE-2026-32740
Debian13libheif1.19.8-1+deb13u1DEBIAN-CVE-2026-32740 DSA-6417-1
Debian14libheif1.23.1-1DEBIAN-CVE-2026-32740
Ubuntu25.10libheif1.20.2-1ubuntu0.4UBUNTU-CVE-2026-32740
Ubuntu26.04:LTSlibheif1.21.2-3ubuntu0.1UBUNTU-CVE-2026-32740
SUSELinux Enterprise Module for Desktop Applications 15 SP7, Linux Enterprise Module for Package Hub 15 SP7libheif1.23.0-150700.3.15.1SUSE-SU-2026:2622-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0libheif1.23.0-160000.1.1SUSE-SU-2026:22153-1
openSUSELeap 16.0libheif1.23.0-160000.1.1openSUSE-SU-2026:20974-1
openSUSETumbleweedlibheif1.22.2-1.1openSUSE-SU-2026:10878-1
Alpinev3.23libheif1.23.0-r0ALPINE-CVE-2026-32740
Alpinev3.24libheif1.22.2-r0ALPINE-CVE-2026-32740
Alpaquitastreamlibheif1.22.2-r0BELL-CVE-2026-32740

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; the Alpine secdb, CC BY-SA 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE · Alpine · Alpaquita.

Red Hat

Red Hat rates this Important.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10glycin-loadersNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-32740.

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

References

Check your stackJSON