# CVE-2025-60359: Memory corruption in n/a

> A memory leak in radare2 allows attackers to cause denial of service by exhausting system memory during binary analysis.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Oct 2025
- **Updated:** 20 Oct 2025
- **Also known as:** GHSA-882g-c5mc-4w4f, UBUNTU-CVE-2025-60359

## What is CVE-2025-60359?

CVE-2025-60359 is a medium-severity memory corruption vulnerability in Radare Radare2, published on 17 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

radare2 v5.9.8 and before contains a memory leak in the function r_bin_object_new.

Weakness: CWE-401 (Missing Release of Memory after Effective Lifetime)

## Which versions are affected by CVE-2025-60359?

It affects 1 product.


Products: Radare Radare2.

## How do I fix CVE-2025-60359?

Upgrade to a fixed version.

## Is CVE-2025-60359 being exploited?

There is no known exploitation of CVE-2025-60359 in the wild and no public exploit code.

## Other vulnerabilities in Radare Radare2

- [CVE-2025-1864](https://insights.sbomify.com/CVE-2025-1864/): Buffer Overflow and Potential Code Execution in Radare2 (critical 10.0)
- [CVE-2025-1744](https://insights.sbomify.com/CVE-2025-1744/): Out-of-bounds Write in radare2 (critical 10.0)
- [CVE-2021-32494](https://insights.sbomify.com/CVE-2021-32494/): Denial of service in radare2 (critical 10.0)
- [CVE-2021-32495](https://insights.sbomify.com/CVE-2021-32495/): Use after free in radare2 (critical 10.0)
- [CVE-2024-29646](https://insights.sbomify.com/CVE-2024-29646/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-60359 and fix it if it is affected.

What it is: CVE-2025-60359 is a medium-severity memory corruption vulnerability in Radare Radare2, published on 17 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-60359 in the wild and no public exploit code.

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

## Sources

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

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