{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-26409 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-26409 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-26409 is a high-severity memory corruption vulnerability in AMD 3rd Gen EPYC, published on 10 Jan 2023. 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-2021-26409 and fix it if it is affected.\n\nWhat it is: CVE-2021-26409 is a high-severity memory corruption vulnerability in AMD 3rd Gen EPYC, published on 10 Jan 2023. 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-2021-26409 in the wild and no public exploit code.\n\nAffected product: AMD 3rd Gen EPYC. 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-2021-26409/ (Markdown: https://insights.sbomify.com/CVE-2021-26409/index.md)","id":"CVE-2021-26409","markdown":"https://insights.sbomify.com/CVE-2021-26409/index.md","name":"CVE-2021-26409","record":{"aliases":["GHSA-53r6-9q9v-359p"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"AMD EPYC firmware","requires_auth":"low_privilege","summary":"Insufficient bounds checking in AMD SEV-ES allows attackers to corrupt Reverse Map table memory, compromising Secure Nested Paging integrity.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"AMD","cpe":[{"product":"milanpi_firmware","vendor":"amd"}],"cvss":{"score":7.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-120","name":"Buffer Copy without Checking Size of Input"}],"description":"Insufficient bounds checking in SEV-ES may allow an attacker to corrupt Reverse Map table (RMP) memory, potentially resulting in a loss of SNP (Secure Nested Paging) memory integrity.","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 3rd Gen EPYC","id":"CVE-2021-26409","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"Information disclosure in AMD Radeon™ PRO V520","id":"CVE-2021-26410"},"packages":[],"prev":{"headline":"Other in 1st Gen AMD EPYC™","id":"CVE-2021-26408"},"products":["3rd Gen EPYC"],"published":"2023-01-10","related":[{"cvss_score":7.5,"headline":"Denial of service in 2nd Gen EPYC","id":"CVE-2023-20522","kev_date_added":null,"published":"2023-01-10"},{"cvss_score":7.1,"headline":"Memory corruption in 1st Gen EPYC","id":"CVE-2021-46779","kev_date_added":null,"published":"2023-01-10"},{"cvss_score":6.1,"headline":"Other in 2nd Gen EPYC","id":"CVE-2021-46767","kev_date_added":null,"published":"2023-01-10"},{"cvss_score":5.5,"headline":"Denial of service in 2nd Gen EPYC","id":"CVE-2021-46768","kev_date_added":null,"published":"2023-01-10"},{"cvss_score":5.5,"headline":"Memory corruption in 3rd Gen EPYC","id":"CVE-2021-46791","kev_date_added":null,"published":"2023-01-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":"total"},"state":"PUBLISHED","updated":"2025-04-09","vendors":["AMD"]},"summary":"Insufficient bounds checking in AMD SEV-ES allows attackers to corrupt Reverse Map table memory, compromising Secure Nested Paging integrity.","url":"https://insights.sbomify.com/CVE-2021-26409/"}