CVE-2026-32882
libheif: Heap Buffer OOB Read in overlay compositing due to wrong alpha stride
No known exploitation. EPSS puts it in the 34th percentile. No fix published yet.
What to do
No fixed build or workaround is published yet. Limit exposure and watch for a patch.
Steps
Written by AI from the record- Check whether your applications, servers, scanners, or image tools use libheif 1.21.2 or earlier.
- Upgrade libheif to version 1.22.0.
- Until upgraded, block or quarantine HEIF files from untrusted senders before they are opened or processed.
- Review recent crashes and unexpected output from software that processes HEIF images.
What it is
From the CVE record
libheif is a HEIF and AVIF file format decoder and encoder. Versions 1.21.2 and prior contain a heap buffer over-read in HeifPixelImage::overlay() in libheif/pixelimage.cc. When compositing an overlay image (iovl) whose child image has a different bit depth for the alpha channel than for the color channels, the function indexes into the alpha plane using the color channel stride (in_stride) instead of the previously retrieved alpha_stride, causing reads past the end of the alpha buffer (up to 3,123 bytes for a 100×50 image with 10-bit color and 8-bit alpha). A crafted HEIF file can exploit this to cause a denial of service (crash) or potentially disclose adjacent heap memory through leaked bytes embedded in the decoded output pixels. This issue has been fixed in versionThis issue has been fixed in version 1.22.0.
In plain language
Written by AI from the recordlibheif 1.21.2 and earlier can be tricked by a malicious image file into crashing software or exposing small amounts of memory, so businesses that open untrusted HEIF images should act urgently.
CWE-125 heap buffer over-read in libheif overlay compositing occurs when a crafted HEIF file uses an alpha channel with a different bit depth from its color channels, causing the wrong stride to index the alpha buffer.
If you're affected
- Image-processing service crashes
- Small memory-data exposure
- Interrupted file-processing workflows
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.4% chance of exploitation activity in the next 30 days, which ranks it in the 34th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
- Attention now
Sustained, driven by in-the-wild reports.
Lifecycle
7 events over 66 days, from the signal feeds we watch.
- Record updated
- Record updated
- Record updated
- OpenVAS check added
- Publishedweakness classified, att&ck mapped
Affected products
Technical detail
CVSS 3.1 vector
Open in the CVSS calculatorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:H
Scored 7.1 by NVD.
How it is reached
- Attack Vector NetworkExploitable remotely over the network without any special conditions
- Attack Complexity LowNo special conditions — the attack can be reliably reproduced
- Privileges Required NoneNo authentication required — anyone can exploit this
- User Interaction RequiredA user must click a link, open a file, or perform some action
Scope
- Scope UnchangedImpact is limited to the vulnerable component itself
Impact if exploited
- Confidentiality LowSome restricted information is disclosed, but limited in scope
- Integrity NoneNo integrity impact
- Availability HighTotal denial of service — the component is completely unavailable
Weaknesses
ATT&CK techniques
Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.
Sources
References in the record
- github.com/strukturag/libheif/releases/tag/v1.22.0
- github.com/strukturag/libheif/security/advisories/GHSA-hg7q-rjr2-8x46
- access.redhat.com/security/cve/CVE-2026-32882
And 2 more references. See all after sign-in
In the news
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Libheif, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI