Skip to main content
VulnerabilityPublished

CVE-2026-50142: strukturag libheif · Integer Overflow or Wraparound

Affects strukturag libheifSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 1.23.0 soon.

Data as of 16 Nov 2026, 20:25 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.23.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    Public exploit code: GitHub proofs of concept

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Upgrade libheif and strukturag/libheif to 1.23.0.

Affected software

ProductAffectedFixed in
strukturaglibheifAffected
  • >=1.19.0 <1.23.0
Fixed in
  • 1.23.0
GitHubstrukturag/libheifpkg:github/strukturag/libheifOther threatsAffected
  • >=1.19.0 <1.23.0
Fixed in
  • 1.23.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade libheif to version 1.23.0 or later, where this vulnerability is fixed. No other mitigation or workaround is indicated by the vendor advisory.

Description

A high-severity integer overflow vulnerability exists in libheif versions 1.19.0 through 1.22.999, affecting the parsing of HEIF sequences with the msf1 brand. The flaw allows crafted input to cause unbounded heap allocation due to improper bounds checking and 32-bit arithmetic wraparound, potentially leading to memory exhaustion and process crashes. This issue is fixed in version 1.23.0.

References

Community reviews

Loading reviews…