# CVE-2026-40499: radare2 < 6.1.4 Command Injection via PDB Parser print_gvars()

> Attackers can execute arbitrary commands by crafting a malicious PDB file with injected newlines in section names, affecting radare2 users.

- **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:** 15 Apr 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-7rhq-9q45-5gm4, MGASA-2026-0198, UBUNTU-CVE-2026-40499, openSUSE-SU-2026:10555-1

## What is CVE-2026-40499?

CVE-2026-40499 is a high-severity command injection vulnerability in Radare Radare2, published on 15 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 version 6.1.4 contains a command injection vulnerability in the PDB parser's print_gvars() function that allows attackers to execute arbitrary commands by embedding a newline byte in the PE section header name field. Attackers can craft a malicious PDB file with specially crafted section names to inject r2 commands that are executed when the idp command processes the file.

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

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `radare2` | openSUSE:Tumbleweed | All versions | 6.1.4-1.1 |

Products: Radare Radare2.

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

Upgrade to a fixed version.

## Is CVE-2026-40499 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-40499 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-40499 and fix it if it is affected.

What it is: CVE-2026-40499 is a high-severity command injection vulnerability in Radare Radare2, published on 15 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-40499 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-40499/ (Markdown: https://insights.sbomify.com/CVE-2026-40499/index.md)
```

## Sources

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

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