{"answers":{"affected":"2 open source packages ship an affected version, including exifreader.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-85715 exists.","fix":"Upgrade exifreader to 4.41.1 or later.","what":"CVE-2026-85715 is a high-severity denial of service vulnerability in mattiasw ExifReader, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-85715 and fix it if it is affected.\n\nWhat it is: CVE-2026-85715 is a high-severity denial of service vulnerability in mattiasw ExifReader, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-85715 exists.\n\nAffected packages and fixed versions:\n- exifreader (npm): affected all versions; fixed in 4.41.1\n- exifreader (npm): affected all versions; fixed in 4.41.1\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-85715/ (Markdown: https://insights.sbomify.com/CVE-2026-85715/index.md)","id":"CVE-2026-85715","markdown":"https://insights.sbomify.com/CVE-2026-85715/index.md","name":"CVE-2026-85715","record":{"aliases":["GHSA-pj96-35fp-cfcc"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript Exif parser","requires_auth":"none","summary":"Attackers can cause memory exhaustion and crash applications by providing crafted HEIC or AVIF images to the ExifReader library.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-835","name":"Loop with Unreachable Exit Condition"},{"id":"CWE-789","name":"Memory Allocation with Excessive Size Value"}],"description":"ExifReader is a JavaScript Exif information parser. Prior to 4.41.1, ExifReader parses attacker-controlled HEIC or AVIF ISO-BMFF files in getItems() within src/image-header-iso-bmff-iloc.js and trusts iloc itemCount and extentCount values while allocating an extent object for every nested-loop iteration. When offsetSize, lengthSize, baseOffsetSize, and indexSize are zero, the extent fields consume no input bytes and the buffer offset does not advance, but the parser can still allocate up to itemCount multiplied by extentCount objects without an allocation budget. A small malicious iloc box can therefore cause hundreds of megabytes of heap growth or exhaust system memory, terminating a Node.js process and denying service to web, desktop, or mobile applications that parse untrusted images. The zero field widths are valid ISO-BMFF values indicating absent fields, so the vulnerable parser must bound work rather than relying on offset advancement. The issue is fixed in version 4.41.1.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"ExifReader: DoS via Crafted HEIC/AVIF iloc Box - Memory Exhaustion","id":"CVE-2026-85715","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"AsyncHttpClient: SCRAM and Digest mutual-authentication responses are not verified","id":"CVE-2026-85716"},"packages":[{"ecosystem":"npm","fixed":["4.41.1"],"introduced":["0"],"last_affected":[],"package":"exifreader","purl":null,"source":"GHSA-pj96-35fp-cfcc"},{"ecosystem":"npm","fixed":["4.41.1"],"introduced":["0"],"last_affected":[],"package":"exifreader","purl":"pkg:npm/exifreader","source":"GHSA-pj96-35fp-cfcc"}],"prev":{"headline":"Stirling-PDF: Remote Code Execution via H2","id":"CVE-2026-85714"},"products":["ExifReader"],"published":"2026-09-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-17","vendors":["mattiasw"]},"summary":"Attackers can cause memory exhaustion and crash applications by providing crafted HEIC or AVIF images to the ExifReader library.","url":"https://insights.sbomify.com/CVE-2026-85715/"}