{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-70631 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-70631 is a medium-severity vulnerability in Ffmpeg Ffmpeg, published on 6 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-70631 and fix it if it is affected.\n\nWhat it is: CVE-2026-70631 is a medium-severity vulnerability in Ffmpeg Ffmpeg, published on 6 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-70631 in the wild and no public exploit code.\n\nAffected product: Ffmpeg Ffmpeg. 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-70631/ (Markdown: https://insights.sbomify.com/CVE-2026-70631/index.md)","id":"CVE-2026-70631","markdown":"https://insights.sbomify.com/CVE-2026-70631/index.md","name":"CVE-2026-70631","record":{"aliases":["DEBIAN-CVE-2026-70631","ECHO-fb13-cd27-af33","GHSA-5f73-3r3j-p8mr","JLSEC-2026-1191","UBUNTU-CVE-2026-70631"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"FFmpeg multimedia library","requires_auth":"none","summary":"Attackers can expose sensitive heap memory data by crafting TIFF files that trigger uninitialized memory reads in FFmpeg's TIFF decoder.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"ffmpeg","vendor":"ffmpeg"}],"cvss":{"score":6.8,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-908","name":"Use of Uninitialized Resource"}],"description":"FFmpeg versions from 0.5 up to, but not including, 9.0 contain an uninitialized heap memory disclosure vulnerability in the native TIFF decoder in libavcodec/tiff.c. An attacker who can cause FFmpeg to decode a crafted TIFF file can supply a valid Deflate-compressed strip that terminates successfully after producing fewer bytes than the declared strip requires. The tiff_unpack_zlib() function allocates a heap buffer sized for the full declared strip but copies all declared rows via memcpy() regardless of how many bytes zlib actually decompressed, causing unwritten bytes that can contain stale data from prior heap allocations to be incorporated into decoded image output and potentially exposing sensitive data in persistent services.","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":"FFmpeg 0.5 \u003c 9.0 Uninitialized Heap Memory Read in TIFF Decoder","id":"CVE-2026-70631","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"ffmpeg:ffmpeg","products":["ffmpeg:ffmpeg"],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"FFmpeg 4.4 \u003c 9.0 Heap Out-of-Bounds Write in CFHD Decoder via AVI Demuxing","id":"CVE-2026-70632"},"packages":[],"prev":{"headline":"FFmpeg 3.0 \u003c 9.0 Uninitialized Heap Memory Read in Screenpresso Decoder","id":"CVE-2026-70630"},"products":["FFmpeg"],"published":"2026-08-06","related":[{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2013-0864","kev_date_added":null,"published":"2013-11-23"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2013-0872","kev_date_added":null,"published":"2013-11-23"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2013-0873","kev_date_added":null,"published":"2013-11-23"},{"cvss_score":10,"headline":"Null dereference in n/a","id":"CVE-2013-4265","kev_date_added":null,"published":"2013-11-23"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2011-3937","kev_date_added":null,"published":"2013-01-05"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2012-2772","kev_date_added":null,"published":"2012-09-10"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2012-2775","kev_date_added":null,"published":"2012-09-10"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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-14","vendors":["FFmpeg"]},"summary":"Attackers can expose sensitive heap memory data by crafting TIFF files that trigger uninitialized memory reads in FFmpeg's TIFF decoder.","url":"https://insights.sbomify.com/CVE-2026-70631/"}