{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-40517 exists.","fix":"Upgrade to a fixed version.","what":"CVE-2026-40517 is a high-severity command injection vulnerability in Radare Radare2, published on 22 Apr 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-40517 and fix it if it is affected.\n\nWhat it is: CVE-2026-40517 is a high-severity command injection vulnerability in Radare Radare2, published on 22 Apr 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-40517 exists.\n\nAffected product: Radare Radare2. 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-40517/ (Markdown: https://insights.sbomify.com/CVE-2026-40517/index.md)","id":"CVE-2026-40517","markdown":"https://insights.sbomify.com/CVE-2026-40517/index.md","name":"CVE-2026-40517","record":{"aliases":["GHSA-3xv9-7r7g-8q6f","UBUNTU-CVE-2026-40517"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"radare2 reverse engineering tool","requires_auth":"none","summary":"Attackers can execute arbitrary OS commands by tricking users into opening a malicious PDB file with crafted symbol names in radare2.","user_interaction":"required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"radare2","vendor":"radare"}],"cvss":{"score":8.4,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"description":"radare2 prior to 6.1.4 contains a command injection vulnerability in the PDB parser's print_gvars() function that allows attackers to execute arbitrary commands by crafting a malicious PDB file with newline characters in symbol names. Attackers can inject arbitrary radare2 commands through unsanitized symbol name interpolation in the flag rename command, which are then executed when a user runs the idp command against the malicious PDB file, enabling arbitrary OS command execution through radare2's shell execution operator.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"radare2 \u003c 6.1.4 Command Injection via PDB Parser Symbol Names","id":"CVE-2026-40517","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"radare:radare2","products":["radare:radare2"],"type":"command_injection","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"ByteDance DeerFlow Path Traversal and Arbitrary File Write via Bootstrap Mode","id":"CVE-2026-40518"},"packages":[],"prev":{"headline":"OpenHarness SSRF via web_fetch and web_search","id":"CVE-2026-40516"},"products":["radare2"],"published":"2026-04-22","related":[{"cvss_score":10,"headline":"Buffer Overflow and Potential Code Execution in Radare2","id":"CVE-2025-1864","kev_date_added":null,"published":"2025-03-03"},{"cvss_score":10,"headline":"Out-of-bounds Write in radare2","id":"CVE-2025-1744","kev_date_added":null,"published":"2025-02-28"},{"cvss_score":10,"headline":"Denial of service in radare2","id":"CVE-2021-32494","kev_date_added":null,"published":"2023-07-07"},{"cvss_score":10,"headline":"Use after free in radare2","id":"CVE-2021-32495","kev_date_added":null,"published":"2023-07-07"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2024-29646","kev_date_added":null,"published":"2024-12-17"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2023-46569","kev_date_added":null,"published":"2023-10-28"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2023-46570","kev_date_added":null,"published":"2023-10-28"}],"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":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-14","vendors":["radareorg"]},"summary":"Attackers can execute arbitrary OS commands by tricking users into opening a malicious PDB file with crafted symbol names in radare2.","url":"https://insights.sbomify.com/CVE-2026-40517/"}