{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-36909 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-36909 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-36909 is a medium-severity vulnerability in n/a, published on 1 Jul 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-36909 and fix it if it is affected.\n\nWhat it is: CVE-2026-36909 is a medium-severity vulnerability in n/a, published on 1 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-36909 in the wild and no public exploit code.\n\nAffected product: n/a. 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-36909/ (Markdown: https://insights.sbomify.com/CVE-2026-36909/index.md)","id":"CVE-2026-36909","markdown":"https://insights.sbomify.com/CVE-2026-36909/index.md","name":"CVE-2026-36909","record":{"aliases":["GHSA-2hw2-5mr3-w7wm"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"MPC-BE media player","requires_auth":"none","summary":"Attackers can cause a Denial of Service in MPC-BE by tricking users into opening a crafted MP4 file, leading to a crash.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":6.2,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-476","name":"NULL Pointer Dereference"}],"description":"A NULL pointer dereference in the AP4_TkhdAtom::GetTrackId() function of Aleksoid1978 MPC-BE before commit 4341cb3 allows attackers to cause a Denial of Service (DoS) via a crafted MP4 file.","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":"Null dereference in n/a","id":"CVE-2026-36909","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Denial of service in n/a","id":"CVE-2026-36910"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2026-36908"},"products":["n/a"],"published":"2026-07-01","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-07-02","vendors":["n/a"]},"summary":"Attackers can cause a Denial of Service in MPC-BE by tricking users into opening a crafted MP4 file, leading to a crash.","url":"https://insights.sbomify.com/CVE-2026-36909/"}