{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-0482 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-0482 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-0482 is a medium-severity memory corruption vulnerability in AMD Alveo™ Accelerator Cards, published on 5 Oct 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-0482 and fix it if it is affected.\n\nWhat it is: CVE-2026-0482 is a medium-severity memory corruption vulnerability in AMD Alveo™ Accelerator Cards, published on 5 Oct 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-0482 in the wild and no public exploit code.\n\nAffected product: AMD Alveo™ Accelerator Cards. 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-0482/ (Markdown: https://insights.sbomify.com/CVE-2026-0482/index.md)","id":"CVE-2026-0482","markdown":"https://insights.sbomify.com/CVE-2026-0482/index.md","name":"CVE-2026-0482","record":{"aliases":["GHSA-w4wm-q9h6-q3vf"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"AMD Versal Adaptive SoC","requires_auth":"none","summary":"Attackers with physical access can execute arbitrary code during boot via buffer overflow in USB boot mode on AMD Versal devices.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"AMD","cpe":[],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:P/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L","version":"4.0"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"In AMD Versal™ Adaptive SoC devices, insufficient boundary checks in USB boot mode—when enabled through board modifications—could allow crafted images to trigger a buffer overflow and overwrite an active function pointer, which may result in arbitrary code execution during boot process. This condition could lead to potential impacts on confidentiality, integrity, and availability.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Memory corruption in Alveo™ Accelerator Cards","id":"CVE-2026-0482","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Stored Cross-Site Scripting (XSS) vulnerability in LiveHelperChat","id":"CVE-2026-0483"},"packages":[],"prev":{"headline":"Misconfiguration in AMD Instinct™ MI210","id":"CVE-2026-0481"},"products":["Alveo™ Accelerator Cards","Versal Premium Series Gen 2 Adaptive SOCs (2VP3402, 2VP3502, 2VP3602)","Versal™ AI Core Series Adaptive SoCs","Versal™ AI Edge Series Adaptive SoCs","Versal™ HBM Series Adaptive SoCs","Versal™ Premium Series Adaptive SoCs","Versal™ Prime Series Adaptive SoCs","Versal™ RF Series Adaptive SoCs"],"published":"2026-10-05","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":"total"},"state":"PUBLISHED","updated":"2026-10-06","vendors":["AMD"]},"summary":"Attackers with physical access can execute arbitrary code during boot via buffer overflow in USB boot mode on AMD Versal devices.","url":"https://insights.sbomify.com/CVE-2026-0482/"}