Process termination via unchecked Lua metadata reads
Published Sep 22, 2026 · Updated Sep 22, 2026
Out-of-bounds read in radare2 before 6.2.0 allows attackers to terminate the process by opening a crafted Lua 5.3 bytecode file. The Lua 5.3 function parser reads two integers and three one-byte metadata fields after a boundary-ending function-name string without checking the remaining buffer length. Exploitation requires a user to open or inspect the file with radare2 or rabin2; observed effects are invalid parser results or a crash, not attacker-visible memory disclosure.
Summary
What happened
Out-of-bounds read in radare2 before 6.2.0 allows attackers to terminate the process by opening a crafted Lua 5.3 bytecode file. The Lua 5.3 function parser reads two integers and three one-byte metadata fields after a boundary-ending function-name string without checking the remaining buffer length. Exploitation requires a user to open or inspect the file with radare2 or rabin2; observed effects are invalid parser results or a crash, not attacker-visible memory disclosure.
The record
- CVE
- CVE-2026-81883
- Published
- Sep 22, 2026
- Updated
- Sep 22, 2026
- Vendor
- radareorg
- Product
- radare2
- Classifications
- CWE-125, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 22, 2026CVE publishedPublication date reported by the CVE source.
- Sep 22, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 6.2.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started