---
id: CVE-2026-81883
title: radare2 is a UNIX-like reverse engineering framework and command-line toolset
summary: >-
  radare2 is a UNIX-like reverse engineering framework and command-line toolset.
  Prior to 6.2.0, radare2's Lua 5.3 bytecode function parser was vulnerable
  because the Lua 5.3 bytecode function parser read fixed function-metadata
  fields imm…
severity: low
cvss: 3.3
cvssVector: 'CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L'
cwe:
  - CWE-125
vendor: radareorg
product: radare2
affected:
  - radare2 < 6.2.0
published: '2026-09-22'
updated: '2026-09-23'
sourceUpdated: '2026-09-23T18:21:42.327'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-81883'
references:
  - url: >-
      https://github.com/radareorg/radare2/commit/26c2eac360033458e9d266e5e30667d1f8d642e3
    label: security-advisories@github.com
  - url: 'https://github.com/radareorg/radare2/issues/26228'
    label: security-advisories@github.com
  - url: 'https://github.com/radareorg/radare2/releases/tag/6.2.0'
    label: security-advisories@github.com
  - url: >-
      https://github.com/radareorg/radare2/security/advisories/GHSA-96m5-hvwp-674c
    label: security-advisories@github.com
  - url: 'https://github.com/radareorg/radare2/issues/26228'
    label: 134c704f-9b21-4f2e-91b3-4a467353bcc0
tags:
  - nvd
  - cve.org
  - exploit-available
epss: 0.00177
epssPercentile: 0.06472
exploitAvailable: true
ssvc:
  exploitation: poc
  automatable: 'no'
  technicalImpact: partial
  timestamp: '2026-09-22T16:11:00.525508Z'
ingestedAt: '2026-09-22T16:06:00.499Z'
---

## Overview

radare2 is a UNIX-like reverse engineering framework and command-line toolset. Prior to 6.2.0, radare2's Lua 5.3 bytecode function parser was vulnerable because the Lua 5.3 bytecode function parser read fixed function-metadata fields immediately after a function-name string without checking the remaining buffer length. The vulnerability is triggered by opening or inspecting a crafted Lua 5.3 bytecode file whose function-name string ends at the input-buffer boundary. The parser read two integers and three one-byte fields beyond the allocated input buffer. This can cause invalid parser results or process termination; no attacker-observable memory disclosure has been demonstrated. This issue is fixed in version 6.2.0.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.