Quick answers
- Is CVE-2026-108387 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-108387 being exploited in the wild.
- How severe is CVE-2026-108387?
- Informational severity, published 4 November 2026.
- Which products and versions are affected?
- Radare2 before 6.2.2.
- Is there a fix for CVE-2026-108387?
- Yes: fixed in 6.2.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-108387 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-108387?
- Check whether you run Radare2 at an affected version. 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.
How to fix
- Fixed in: 6.2.2
Technical details
A command injection vulnerability exists in radare2's binary format plugins where attacker-controlled data from Pebble and Sega Mega Drive binaries can reach the RBinInfo->bclass field. By injecting a dbg:// URI into bclass, the tool automatically reopens the input through the debug I/O plugin and passes attacker-controlled arguments to execvp(), bypassing the need for explicit debugging commands. This allows arbitrary command execution in the context of the radare2 process.
Affected products
- radare radare2 before 6.2.2
Timeline
- 2026-11-04: disclosed
- 2026-11-04: patched