CVE-2026-84450: libheif assertion failure in clap property crop calculation

CVE-2026-84450 · Severity: medium · CVSS 4.3 · Published 2026-09-18

libheif is a decoder and encoder for HEIF and AVIF image formats. A crafted image file with an oversized width or height property combined with a crop region property can trigger an assertion failure in builds compiled with debugging enabled, causing the application to abort. Release builds compute invalid crop geometry instead, which the tiling API may then reject as exceeding security limits.

Technologies: Strukturag Libheif. Vendors: Strukturag.

Quick answers

Is CVE-2026-84450 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-84450 being exploited in the wild.
How severe is CVE-2026-84450?
Medium severity, with a CVSS score of 4.3, published 18 September 2026.
Which products and versions are affected?
Strukturag Libheif 1.19.0 to 1.23.2.
Is there a fix for CVE-2026-84450?
A patch was published on 2026-09-01. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-84450 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-84450?
Check whether you run Strukturag Libheif at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A clap (crop/aperture) property combined with an ispe (image spatial extents) dimension exceeding INT32_MAX+1 reaches the Fraction constructor through Box_clap::left_rounded() or Box_clap::top_rounded(), which only asserts its input range. This causes abort in assert-enabled builds, or computes incorrect crop geometry in release builds. The fix replaces the asserting constructor with error-returning factories and validates image size at the Box_clap::get_crop() entry point.

Affected products

  • strukturag libheif 1.19.0 to 1.23.2

Timeline

  • 2026-09-18: disclosed
  • 2026-09-01: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.