CVE-2026-40517

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-04-23. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.8
EG Score
7.8(medium)
EPSS
60.4%
KEV
Not listed

Published

April 22, 2026

Last Modified

July 14, 2026

Advisory Details (4)

Auto-updated Jun 4, 2026
Upstream fix merged — awaiting tagged release. Sources: github_pr.
generic

radare2 < 6.1.4 Command Injection via PDB Parser Symbol Names | Advisories | VulnCheck

https://www.vulncheck.com/advisories/radare2-command-injection-via-pdb-parser-symbol-names
github_pr

Fix #25730 - Base64 encode PDB realnames before use in r2 command

Fix merged in radareorg/radare2 PR #25731 on 2026-04-06 — awaiting tagged release

https://github.com/radareorg/radare2/pull/25731
generic

[Security] Command injection caused by lack of sanitization of PDB symbol names · Issue #25730 · radareorg/radare2 · GitHub

https://github.com/radareorg/radare2/issues/25730
generic

MAD Bugs: Discovering a 0-Day in Zero Day - Calif

https://blog.calif.io/p/mad-bugs-discovering-a-0-day-in-zero

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 36× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 123 total refreshes for this CVE.

  1. 2026-07-15 16:57 UTCEPSS rescore
  2. 2026-07-15 16:57 UTCEPSS rescore
  3. 2026-07-15 02:00 UTCEPSS rescore
  4. 2026-07-13 22:30 UTCEPSS rescore
  5. 2026-07-13 06:13 UTCEPSS rescore
  6. 2026-07-13 06:13 UTCEPSS rescore
  7. 2026-07-12 05:46 UTCEPSS rescore
  8. 2026-07-11 08:27 UTCEPSS rescore
  9. 2026-07-09 19:10 UTCEPSS rescore
  10. 2026-07-08 15:15 UTCEPSS rescore
  11. 2026-07-07 13:46 UTCEPSS rescore
  12. 2026-07-06 16:27 UTCEPSS rescore
  13. 2026-07-06 16:27 UTCEPSS rescore
  14. 2026-07-06 02:23 UTCEPSS rescore
  15. 2026-07-06 02:23 UTCEPSS rescore
  16. 2026-07-05 02:30 UTCEPSS rescore
  17. 2026-07-04 06:31 UTCEPSS rescore
  18. 2026-07-01 15:06 UTCEPSS rescore
  19. 2026-06-30 23:22 UTCEPSS rescore
  20. 2026-06-28 14:07 UTCEPSS rescore
  21. 2026-06-28 04:56 UTCEPSS rescore
  22. 2026-06-27 03:08 UTCEPSS rescore
  23. 2026-06-25 13:49 UTCEPSS rescore
  24. 2026-06-25 13:49 UTCEPSS rescore
  25. 2026-06-24 14:05 UTCEPSS rescore
Show 75 more
  1. 2026-06-23 21:33 UTCEPSS rescore
  2. 2026-06-22 14:25 UTCEPSS rescore
  3. 2026-06-22 14:25 UTCEPSS rescore
  4. 2026-06-21 14:56 UTCEPSS rescore
  5. 2026-06-21 14:56 UTCEPSS rescore
  6. 2026-06-21 01:59 UTCEPSS rescore
  7. 2026-06-19 19:25 UTCEPSS rescore
  8. 2026-06-18 17:52 UTCEPSS rescore
  9. 2026-06-18 17:52 UTCEPSS rescore
  10. 2026-06-17 17:53 UTCEPSS rescore
  11. 2026-06-16 17:52 UTCEPSS rescore
  12. 2026-06-15 17:49 UTCEPSS rescore
  13. 2026-06-15 02:32 UTCEG score recompute
  14. 2026-06-15 02:32 UTCGHSA enrichment
  15. 2026-06-14 12:27 UTCEG score recompute
  16. 2026-06-14 12:27 UTCGHSA enrichment
  17. 2026-06-13 23:00 UTCEPSS rescore
  18. 2026-06-12 23:12 UTCEPSS rescore
  19. 2026-06-12 23:12 UTCEPSS rescore
  20. 2026-06-12 03:34 UTCEG score recompute
  21. 2026-06-12 03:34 UTCGHSA enrichment
  22. 2026-06-11 14:32 UTCEG score recompute
  23. 2026-06-11 14:32 UTCGHSA enrichment
  24. 2026-06-11 14:00 UTCEPSS rescore
  25. 2026-06-10 22:18 UTCEPSS rescore
  26. 2026-06-10 18:37 UTCEG score recompute
  27. 2026-06-10 18:37 UTCGHSA enrichment
  28. 2026-06-10 13:22 UTCEPSS rescore
  29. 2026-06-10 13:22 UTCEPSS rescore
  30. 2026-06-10 05:36 UTCEG score recompute
  31. 2026-06-10 05:36 UTCGHSA enrichment
  32. 2026-06-09 16:35 UTCEG score recompute
  33. 2026-06-09 16:35 UTCGHSA enrichment
  34. 2026-06-09 03:34 UTCEG score recompute
  35. 2026-06-09 03:34 UTCGHSA enrichment
  36. 2026-06-08 14:17 UTCEPSS rescore
  37. 2026-06-08 14:17 UTCEPSS rescore
  38. 2026-06-08 09:49 UTCEG score recompute
  39. 2026-06-08 09:49 UTCGHSA enrichment
  40. 2026-06-07 20:48 UTCEG score recompute
  41. 2026-06-07 20:48 UTCGHSA enrichment
  42. 2026-06-07 15:25 UTCEPSS rescore
  43. 2026-06-07 15:25 UTCEPSS rescore
  44. 2026-06-07 07:46 UTCEG score recompute
  45. 2026-06-07 07:46 UTCGHSA enrichment
  46. 2026-06-06 18:45 UTCEG score recompute
  47. 2026-06-06 18:45 UTCGHSA enrichment
  48. 2026-06-06 13:47 UTCEPSS rescore
  49. 2026-06-06 13:47 UTCEPSS rescore
  50. 2026-06-06 05:44 UTCEG score recompute
  51. 2026-06-06 05:44 UTCGHSA enrichment
  52. 2026-06-05 22:47 UTCEPSS rescore
  53. 2026-06-05 16:43 UTCEG score recompute
  54. 2026-06-05 16:43 UTCGHSA enrichment
  55. 2026-06-05 06:10 UTCEPSS rescore
  56. 2026-06-05 06:10 UTCEPSS rescore
  57. 2026-06-05 03:35 UTCEG score recompute
  58. 2026-06-05 03:35 UTCGHSA enrichment
  59. 2026-06-04 14:34 UTCEG score recompute
  60. 2026-06-04 14:34 UTCGHSA enrichment
  61. 2026-06-04 13:12 UTCEPSS rescore
  62. 2026-06-04 13:12 UTCEPSS rescore
  63. 2026-06-04 01:29 UTCEG score recompute
  64. 2026-06-04 01:29 UTCGHSA enrichment
  65. 2026-06-03 12:24 UTCEG score recompute
  66. 2026-06-03 12:24 UTCGHSA enrichment
  67. 2026-06-02 20:13 UTCEPSS rescore
  68. 2026-06-02 16:38 UTCEG score recompute
  69. 2026-06-02 16:38 UTCGHSA enrichment
  70. 2026-06-02 03:36 UTCEG score recompute
  71. 2026-06-02 03:36 UTCGHSA enrichment
  72. 2026-06-01 14:34 UTCEG score recompute
  73. 2026-06-01 14:34 UTCGHSA enrichment
  74. 2026-06-01 13:52 UTCEPSS rescore
  75. 2026-06-01 13:52 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-40517?
CVE-2026-40517 is a high vulnerability published on April 22, 2026. 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…
When was CVE-2026-40517 disclosed?
CVE-2026-40517 was first published in the National Vulnerability Database on April 22, 2026, with the most recent update on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-40517 actively exploited?
CVE-2026-40517 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 60.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-40517?
CVE-2026-40517 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-40517?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-40517, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-40517

Explore →

Is Your Infrastructure Affected by CVE-2026-40517?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.