CVE-2026-32882

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 75% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: Elevated riskExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
48(Track)
EG Risk 48/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity71% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
27%
KEV
Not listed

Published

May 19, 2026

Last Modified

July 24, 2026

Advisory Details (2)

Auto-updated May 20, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Heap Buffer OOB Read in overlay compositing due to wrong alpha stride · Advisory · strukturag/libheif · GitHub

https://github.com/strukturag/libheif/security/advisories/GHSA-hg7q-rjr2-8x46
generic

Release v1.22.0 - generic image components, ISO/IEC 23001-17 (lossless images) rewrite · strukturag/libheif · GitHub

https://github.com/strukturag/libheif/releases/tag/v1.22.0

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibheif1 (1.21.2-3ubuntu0.1) @ resolute2026-08-23ubuntu

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
libheif1.11.0-1 ... 1.23.1-1 (39 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
libheif1.15.1-1 ... 1.23.2-1 (34 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
libheif1.19.8-11.19.8-1+deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
libheif1.19.8-1 ... 1.21.2-4 (8 versions)1.23.1-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

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 6× in last 7d / 29× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 213 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-32882?
CVE-2026-32882 is a high vulnerability published on May 19, 2026. 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…
When was CVE-2026-32882 disclosed?
CVE-2026-32882 was first published in the National Vulnerability Database on May 19, 2026, with the most recent update on July 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-32882 actively exploited?
CVE-2026-32882 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 73.1% of all scored CVEs.
What is the CVSS score of CVE-2026-32882?
CVE-2026-32882 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-32882?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-32882, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-32882

Explore →

Is Your Infrastructure Affected by CVE-2026-32882?

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

Start Free Scan →Browse All CVEs