CVE-2026-14786: radareorg radare2 · Integer Overflow
Affects radareorg radare2Source CVE Database V5
Public exploit available · CVSS 4.8 Medium.
Data as of 17 Nov 2026, 20:25 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 6 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| radareorgradare2 | Affected
| Fixed in– |
GitHubradareorg/radare2pkg:github/radareorg/radare2Other threats | Affected
| Fixed in– |
CPE configurations (1)
cpe:2.3:a:radareorg:radare2:*:*:*:*:*:*:*:*
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch identified by commit 11ac224c0eb8d57830fccc99e1c1cd8e5d958813 is available and should be applied to affected versions 6.1.0 through 6.1.6 of radare2. Applying this patch is the recommended remediation to resolve the vulnerability.
Description
A security flaw has been discovered in radareorg radare2 up to 6.1.6. This impacts the function r_str_word_get0set of the file libr/util/str.c. The manipulation results in integer overflow. The attack must be initiated from a local position. The exploit has been released to the public and may be used for attacks. The patch is identified as 11ac224c0eb8d57830fccc99e1c1cd8e5d958813. It is best practice to apply a patch to resolve this issue.
References
- vuldb.com/vuln/376375 (opens in a new tab)
- vuldb.com/vuln/376375/cti (opens in a new tab)
- vuldb.com/cve/CVE-2026-14786 (opens in a new tab)
- vuldb.com/submit/850386 (opens in a new tab)
- github.com/radareorg/radare2/issues/26047 (opens in a new tab)
- github.com/radareorg/radare2/commit/11ac224c0eb8d57830fccc99e1c1cd8e5d958813 (opens in a new tab)
- github.com/radareorg/radare2/ (opens in a new tab)