{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-62289 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-62289 is a medium-severity vulnerability in strukturag libheif, published on 18 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-62289 and fix it if it is affected.\n\nWhat it is: CVE-2026-62289 is a medium-severity vulnerability in strukturag libheif, published on 18 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-62289 in the wild and no public exploit code.\n\nAffected product: strukturag libheif. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-62289/ (Markdown: https://insights.sbomify.com/CVE-2026-62289/index.md)","id":"CVE-2026-62289","markdown":"https://insights.sbomify.com/CVE-2026-62289/index.md","name":"CVE-2026-62289","record":{"aliases":["BELL-CVE-2026-62289","DEBIAN-CVE-2026-62289","ECHO-ebfc-8101-ce00","GHSA-jc8f-p23p-5hjg","MINI-cmf9-rwvq-rc53"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"HEIF/AVIF image library","requires_auth":"none","summary":"A crafted HEIF or AVIF file triggers an integer underflow in libheif, causing crashes or corrupt tiling results during image processing.","user_interaction":"required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-617","name":"Reachable Assertion"},{"id":"CWE-191","name":"Integer Underflow (Wrap or Wraparound)"}],"description":"libheif is a HEIF and AVIF file format decoder and encoder. In 1.23.0 and earlier, a crafted HEIF or AVIF file containing a clean aperture box can reduce an image dimension to zero and crash or corrupt tiling results when heif_image_handle_get_image_tiling(handle, 1, \u0026tiling) is called. ImageItem::get_heif_image_tiling() returns already transformed dimensions, and process_image_transformations_on_tiling() applies the clean aperture transformation again. The second application passes zero to Box_clap::left_rounded(0), where image_width minus one underflows and constructs Fraction(0xFFFFFFFF, 2). Debug builds reach an assertion and abort, while release builds can return a corrupt crop and zero-width tiling result. The affected implementation spans libheif/image-items/image_item.cc, libheif/context.cc, and libheif/box.cc. This issue is fixed in version 1.23.1.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"libheif: Integer underflow in Fraction constructor via double clap transform application","id":"CVE-2026-62289","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"cert-manager: Direct ACME Challenge resources can bypass Issuer DNS01 solver policy and use ClusterIssuer DNS credentials","id":"CVE-2026-62290"},"packages":[],"prev":{"headline":"Dozzle label filters do not restrict container event and statistics streams","id":"CVE-2026-62286"},"products":["libheif"],"published":"2026-08-18","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-19","vendors":["strukturag"]},"summary":"A crafted HEIF or AVIF file triggers an integer underflow in libheif, causing crashes or corrupt tiling results during image processing.","url":"https://insights.sbomify.com/CVE-2026-62289/"}