# CVE-2026-40517: radare2 < 6.1.4 Command Injection via PDB Parser Symbol Names

> Attackers can execute arbitrary OS commands by tricking users into opening a malicious PDB file with crafted symbol names in radare2.

- **Severity:** High 8.4 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 22 Apr 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-3xv9-7r7g-8q6f, UBUNTU-CVE-2026-40517

## What is CVE-2026-40517?

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.

### Official 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.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2026-40517?

It affects 1 product.


Products: Radare Radare2.

## How do I fix CVE-2026-40517?

Upgrade to a fixed version.

## Is CVE-2026-40517 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-40517 exists.

## Other vulnerabilities in Radare Radare2

- [CVE-2025-1864](https://insights.sbomify.com/CVE-2025-1864/): Buffer Overflow and Potential Code Execution in Radare2 (critical 10.0)
- [CVE-2025-1744](https://insights.sbomify.com/CVE-2025-1744/): Out-of-bounds Write in radare2 (critical 10.0)
- [CVE-2021-32494](https://insights.sbomify.com/CVE-2021-32494/): Denial of service in radare2 (critical 10.0)
- [CVE-2021-32495](https://insights.sbomify.com/CVE-2021-32495/): Use after free in radare2 (critical 10.0)
- [CVE-2024-29646](https://insights.sbomify.com/CVE-2024-29646/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-40517 and fix it if it is affected.

What 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-40517 exists.

Affected product: Radare Radare2. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-40517/ (Markdown: https://insights.sbomify.com/CVE-2026-40517/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-40517
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-40517
- OSV: https://osv.dev/vulnerability/CVE-2026-40517

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-40517/
Summaries are generated and may contain mistakes; the official description above is the record.