# CVE-2026-41015: Command injection in radare2

> An attacker can execute arbitrary commands via a crafted PDB name in radare2 when SSL is disabled on UNIX systems.

- **Severity:** High 7.4 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Apr 2026
- **Updated:** 16 Apr 2026
- **Also known as:** GHSA-v352-gq4q-9qjf, UBUNTU-CVE-2026-41015

## What is CVE-2026-41015?

CVE-2026-41015 is a high-severity command injection vulnerability in radare2, published on 16 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

radare2 before 9236f44, when configured on UNIX without SSL, allows command injection via a PDB name to rabin2 -PP. NOTE: although users are supposed to use the latest version from git (not a release), the date range for the vulnerable code was less than a week, occurring after 6.1.2 but before 6.1.3.

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

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


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

Apply the vendor's patch.

## Is CVE-2026-41015 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-41015 is a high-severity command injection vulnerability in radare2, published on 16 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41015 exists.

Affected product: 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-41015/ (Markdown: https://insights.sbomify.com/CVE-2026-41015/index.md)
```

## Sources

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

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