# CVE-2026-4174: Radare2 Mach-O File mach0.c walk_exports_trie resource consumption

> A local attacker can cause resource consumption in Radare2 via a crafted Mach-O file, leading to denial of service.

- **Severity:** Medium 4.8 (`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:P`)
- **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:** 15 Mar 2026
- **Updated:** 17 Mar 2026
- **Also known as:** GHSA-fwp9-q76v-g574, UBUNTU-CVE-2026-4174

## What is CVE-2026-4174?

CVE-2026-4174 is a medium-severity denial of service vulnerability in Radare2, published on 15 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability has been found in Radare2 5.9.9. This issue affects the function walk_exports_trie of the file libr/bin/format/mach0/mach0.c of the component Mach-O File Parser. Such manipulation leads to resource consumption. The attack can only be performed from a local environment. The exploit has been disclosed to the public and may be used. The existence of this vulnerability is still disputed at present. Upgrading to version 6.1.2 is capable of addressing this issue. The name of the patch is 4371ae84c99c46b48cb21badbbef06b30757aba0. You should upgrade the affected component. The code maintainer states that, "[he] wont consider this bug a DoS".

Weakness: CWE-404 (Improper Resource Shutdown or Release), CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2026-4174?


## How do I fix CVE-2026-4174?

Upgrade to a fixed version.

## Is CVE-2026-4174 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-4174 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-4174 and fix it if it is affected.

What it is: CVE-2026-4174 is a medium-severity denial of service vulnerability in Radare2, published on 15 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-4174 exists.

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

## Sources

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

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