{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-84448 exists.","fix":"Upgrade to a fixed version.","what":"CVE-2026-84448 is a medium-severity vulnerability in strukturag libheif, published on 18 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-84448 and fix it if it is affected.\n\nWhat it is: CVE-2026-84448 is a medium-severity vulnerability in strukturag libheif, published on 18 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-84448 exists.\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-84448/ (Markdown: https://insights.sbomify.com/CVE-2026-84448/index.md)","id":"CVE-2026-84448","markdown":"https://insights.sbomify.com/CVE-2026-84448/index.md","name":"CVE-2026-84448","record":{"aliases":["BELL-CVE-2026-84448","DEBIAN-CVE-2026-84448","ECHO-93e0-e371-957b","GHSA-p58j-h3vm-3fp5","MINI-qv33-x58q-2qcv","UBUNTU-CVE-2026-84448"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"HEIF/AVIF image library","requires_auth":"none","summary":"An attacker can trigger a heap out-of-bounds read in libheif's region API, potentially disclosing sensitive memory or crashing the application.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-131","name":"Incorrect Calculation of Buffer Size"},{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"libheif is a HEIF and AVIF file format decoder and encoder. Prior to 1.23.2, the public heif_region_item_add_region_inline_mask_data() function in libheif/api/libheif/heif_regions.cc accepts mask_data_len without verifying that it equals the byte count required by width and height. A later heif_region_get_mask_image() call derives the read length from the region geometry, so an undersized stored buffer causes heif_region_get_inline_mask_image() to read beyond the heap allocation and copy adjacent bytes into the returned monochrome mask image. This can disclose heap data or crash an application that constructs region metadata through the writer API, while the file-parsing path is not affected because it validates the canonical mask size. This issue is fixed in version 1.23.2.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Information disclosure in libheif","id":"CVE-2026-84448","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"libheif hOp_RGB24_32_to_YCbCr Memory Access Error / SEGV","id":"CVE-2026-84449"},"packages":[],"prev":{"headline":"Denial of service in libheif","id":"CVE-2026-84447"},"products":["libheif"],"published":"2026-09-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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-24","vendors":["strukturag"]},"summary":"An attacker can trigger a heap out-of-bounds read in libheif's region API, potentially disclosing sensitive memory or crashing the application.","url":"https://insights.sbomify.com/CVE-2026-84448/"}