Vulnerability Database · OSS-Fuzz · Package report

radare2: vulnerability history, versions and safety

radare2 is a package in the OSS-Fuzz ecosystem. Vulert records 61 vulnerabilities for it across 67 releases, from Jun 2020 to Jan 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
61 vulnerabilities recorded H26 M30 U5
i
5 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on radare2 i

Updated on 23 Oct 2026

Careful: 5 of the 61 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 61 vulnerabilities on record across 4 years, none in the last year.

What to do: Plan around the 5 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 61 over 4 years · 0 in the last year i
  • Latest disclosure 20 Jan 2025 i
  • Highest CVSS n/a i
  • With no published fix 5 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for radare2, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
5.9.8 H1 M2 U1 No Details →
5.9.6 H1 M2 U1 No Details →
5.9.4 H1 M2 U1 No Details →
5.9.2 H1 M2 U1 No Details →
5.9.0 H1 M2 U1 No Details →
5.8.8 H1 M2 U1 No Details →
5.8.6 H1 M2 U1 No Details →
5.8.4 H1 M2 U1 No Details →
5.8.2 H1 M2 U1 No Details →
5.8.0 H1 M2 U1 No Details →
5.7.8 M1 No Details →
5.7.6 M2 No Details →
5.7.4 M3 No Details →
5.7.2 M3 No Details →
5.7.0 M4 No Details →
5.6.8 M3 No Details →
5.6.6 M3 Yes Details →
5.6.4 M3 Yes Details →
5.6.2 M3 Yes Details →
5.6.0 M3 Yes Details →
5.5.4 M4 Yes Details →
5.5.2 M4 Yes Details →
5.5.0 M4 Yes Details →
5.4.2 M4 Yes Details →
5.4.0 M4 Yes Details →
5.4.0-git M4 Yes Details →
5.3.1 M4 Yes Details →
5.3.0 M4 Yes Details →
5.2.1 M4 Yes Details →
5.2.0 M4 Yes Details →
5.1.1 M4 Yes Details →
5.1.0 M4 Yes Details →
5.0.0 M4 Yes Details →
4.5.1 M4 Yes Details →
4.5.0 M1 Yes Details →
4.4.0 H2 M4 Yes Details →
4.3.1 M2 Yes Details →
4.3.0 M2 Yes Details →
4.2.1 M2 Yes Details →
4.2.0 M2 Yes Details →
4.1.1 M2 Yes Details →
4.1.0 M2 Yes Details →
4.0.0 M2 Yes Details →
3.9.0 M1 Yes Details →
3.8.0 M1 Yes Details →
3.7.1 M1 Yes Details →
3.7.0 H1 M1 Yes Details →
3.6.0 H2 Yes Details →
3.5.1 H4 Yes Details →
3.5.0 H4 Yes Details →
3.4.1 H2 M1 Yes Details →
3.4.0 H2 M2 Yes Details →
3.3.0 H1 M1 Yes Details →
3.2.1 H1 M2 Yes Details →
3.2.0 H1 M2 Yes Details →
3.1.3 H1 M4 Yes Details →
3.1.2 H1 M4 Yes Details →
3.1.1 H1 M4 Yes Details →
3.1.0 H1 M4 Yes Details →
3.0.1 H1 M3 Yes Details →
3.0.0 H1 M3 Yes Details →
2.9.0 H1 M5 Yes Details →
2.8.0 H1 M2 Yes Details →
release-5.0.0 M4 Yes Details →
continuous M3 Yes Details →
wip M1 No Details →
Continuous-Windows M2 Yes Details →

Newest 67 of 67 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 32
  • 2021 9
  • 2022 7
  • 2023 10
  • 2024 1
  • 2025 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 61 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for radare2

The 5 most severe of 61 vulnerabilities recorded for this package

Search all 61 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Stack-use-after-return vulnerability in radare2 N/A unrated No fix published 29 Sep 2022
Critical Stack Buffer Overflow in Radare2: CVE-2024-523 N/A high No fix published 01 Jun 2024
UNKNOWN READ in r_str_ncpy in radare2 N/A medium 59806217f8fdadd4de7d0edab81c40442d9aec75 07 Oct 2023
Heap-buffer-overflow in read_reloc in radare2 N/A high 97f2d9cf5cdaee655e5a5527c78f42715b61ad51 24 Jun 2020
Heap-use-after-free vulnerability in radare2 N/A high 85b4fa4f96db8d1c4fc4315fed93b624e3b1cade 28 Jul 2023

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About radare2

Is radare2 safe to use?

Vulert records 61 vulnerabilities for radare2 in OSS-Fuzz: 0 critical, 26 high, 30 medium and 0 low, plus 5 not yet rated. 5 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does radare2 have?

61 vulnerabilities are recorded for radare2 in the OSS-Fuzz ecosystem: 0 critical, 26 high, 30 medium and 0 low, plus 5 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new radare2 vulnerabilities disclosed?

0 vulnerabilities were recorded for radare2 in the last 12 months, and the oldest entry in this database dates to 24 Jun 2020. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of radare2 are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor radare2 for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the radare2 version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.