# CVE-2026-45613: Rizin: Heap-buffer-overflow in OMF parser

> A heap-buffer-overflow in the OMF parser allows attackers to execute arbitrary code or cause denial of service via crafted binaries.

- **Severity:** Low 3.3 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 29 May 2026
- **Updated:** 1 Jun 2026
- **Also known as:** GHSA-wprr-wrcw-mw6v

## What is CVE-2026-45613?

CVE-2026-45613 is a low-severity memory corruption vulnerability in rizinorg rizin, published on 29 May 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Rizin is a UNIX-like reverse engineering framework and command-line toolset. There is a heap-buffer-overflow in librz/bin/format/omf/omf.c. This vulnerability is fixed by commit e6d0937c8a083e23ed76ccfb9f631cdc50c7af47.

Weakness: CWE-125 (Out-of-bounds Read)

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


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

No fix has been published for CVE-2026-45613 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-45613 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-45613 is a low-severity memory corruption vulnerability in rizinorg rizin, published on 29 May 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-45613 in the wild and no public exploit code.

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

## Sources

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

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