{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-120456 in the wild and no public exploit code.","exposure":"","fix":"No fix has been published for CVE-2026-120456 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-120456 is a medium-severity vulnerability in L-SMASH, published on 2 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2026-120456 and fix it if it is affected.\n\nWhat it is: CVE-2026-120456 is a medium-severity vulnerability in L-SMASH, published on 2 Nov 2026. \nExploitation: There is no known exploitation of CVE-2026-120456 in the wild and no public exploit code.\n\nAffected product: L-SMASH. 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-120456/ (Markdown: https://insights.sbomify.com/CVE-2026-120456/index.md)","id":"CVE-2026-120456","markdown":"https://insights.sbomify.com/CVE-2026-120456/index.md","name":"CVE-2026-120456","record":{"aliases":["GHSA-q7pj-x362-2v3p"],"analysis":null,"analysis_generated_by":null,"assigner":"VulnCheck","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"L-SMASH through 2.14.5 contains a heap out-of-bounds write vulnerability in isom_read_hdlr() and isom_read_dref_entry() in core/read.c triggered by oversized box sizes. Attackers can supply crafted MP4 or MOV files declaring hdlr or url box sizes larger than remaining data, stalling the stream position and corrupting heap memory to crash applications.","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":"L-SMASH through 2.14.5 Heap Out-of-Bounds Write via hdlr and url Boxes","id":"CVE-2026-120456","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"libaec through 1.1.7 Out-of-Bounds Read via m_se_decode() Second Extension Decoder","id":"CVE-2026-120457"},"nickname":null,"packages":[],"prev":{"headline":"rapidyaml through 0.16.0 Out-of-Bounds Write via ParseEngine::_add_annotation()","id":"CVE-2026-120455"},"products":["L-SMASH"],"published":"2026-11-02","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-02","vendors":["L-SMASH"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-120456/"}