Skip to main content
CVE-2024-29646VulnerabilityPublished Updated

CVE-2024-29646: radare2 · n/a

Affects radare2Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.9% chance of exploitation in 30 days – higher than 60% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Dec 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
GitHubradareorg/radare2pkg:github/radareorg/radare2Other threatsAffected
  • =5.8.8
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Monitor official radare2 repositories and security advisories closely for patches addressing CVE-2024-29646 and apply updates immediately upon release. 2. Until patches are available, restrict network access to radare2 instances, limiting exposure to trusted users and internal networks only. 3. Employ application-layer firewalls or intrusion detection systems to detect and block suspicious inputs targeting the name, type, or group fields. 4. Run radare2 with the least privilege necessary to reduce potential impact of exploitation. 5. Use sandboxing or containerization to isolate radare2 processes, minimizing system-wide compromise risk. 6. Conduct regular security audits and code reviews of radare2 usage in your environment to identify anomalous behavior. 7. Educate security teams about this vulnerability to enhance monitoring and incident response readiness. 8. Consider temporary alternative tools for reverse engineering tasks if feasible until the vulnerability is patched.

Description

Buffer Overflow vulnerability in radarorg radare2 v.5.8.8 allows an attacker to execute arbitrary code via the name, type, or group fields.

References

Community reviews

Loading reviews…