{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-125263 in the wild and no public exploit code.","exposure":"","fix":"No fix has been published for CVE-2026-125263 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-125263 is a medium-severity vulnerability in FFmpeg, published on 9 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2026-125263 and fix it if it is affected.\n\nWhat it is: CVE-2026-125263 is a medium-severity vulnerability in FFmpeg, published on 9 Nov 2026. \nExploitation: There is no known exploitation of CVE-2026-125263 in the wild and no public exploit code.\n\nAffected product: 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-125263/ (Markdown: https://insights.sbomify.com/CVE-2026-125263/index.md)","id":"CVE-2026-125263","markdown":"https://insights.sbomify.com/CVE-2026-125263/index.md","name":"CVE-2026-125263","record":{"aliases":["GHSA-9887-9v8v-j28g","UBUNTU-CVE-2026-125263"],"analysis":null,"analysis_generated_by":null,"assigner":"VulnCheck","cpe":[],"cvss":{"score":5.7,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:H/AT:P/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-789","name":"Memory Allocation with Excessive Size Value"}],"description":"FFmpeg 9.0 through 9.0.2 built with liblcevc_dec fails to validate LCEVC enhanced output dimensions against max_pixels in libavcodec/decode.c before frame allocation. Attackers can supply crafted H.264, HEVC or VVC streams declaring huge LCEVC resolutions to force oversized get_buffer2() allocations and exhaust memory.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"FFmpeg 9.0 through 9.0.2 Memory Exhaustion via LCEVC Enhancement Dimensions","id":"CVE-2026-125263","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"FFmpeg through 9.0.2 CPU Exhaustion via JPEG XL Parser TOC Count","id":"CVE-2026-125264"},"nickname":null,"packages":[],"prev":{"headline":"FFmpeg through 9.0.2 Heap Buffer Overflow via LCEVC Enhancement Decoding","id":"CVE-2026-125262"},"products":["FFmpeg"],"published":"2026-11-09","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-11-09","vendors":["FFmpeg"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-125263/"}