CVE-2026-40517: radare2 prior to 6.1.4 contains a command injection vulnerability in the PDB parser's print_gvars() function that…

CVE-2026-40517 · Severity: high · CVSS 7.8 · Published 2026-04-22

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.

Technologies: Radare2. Vendors: Radare.

Quick answers

Is CVE-2026-40517 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-40517 being exploited in the wild.
How severe is CVE-2026-40517?
High severity, with a CVSS score of 7.8, published 22 April 2026.
Which products and versions are affected?
Radare2. The advisory does not name versions.
Is there a fix for CVE-2026-40517?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
Am I affected by CVE-2026-40517?
Check whether you run Radare2. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Affected products

  • Radare2

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.