Memory corruption via mismatched chained-segment bounds
Published Feb 2, 2026 · Updated Feb 2, 2026
Heap overflow in Rizin before 0.8.2 allows local users to corrupt memory by opening a crafted Mach-O file for analysis. The parse_chained_fixups routine iterates to the larger of the Mach-O segment count and allocated starts table, writing past the heap buffer when the counts differ. Exploitation requires user interaction to analyze the file and can corrupt process memory or interrupt the Rizin process; no confidentiality impact is reported.
Summary
What happened
Heap overflow in Rizin before 0.8.2 allows local users to corrupt memory by opening a crafted Mach-O file for analysis. The parse_chained_fixups routine iterates to the larger of the Mach-O segment count and allocated starts table, writing past the heap buffer when the counts differ. Exploitation requires user interaction to analyze the file and can corrupt process memory or interrupt the Rizin process; no confidentiality impact is reported.
The record
- CVE
- CVE-2026-22780
- Published
- Feb 2, 2026
- Updated
- Feb 2, 2026
- Vendor
- Rizin Organization
- Product
- Rizin
- Classifications
- CWE-770, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 2, 2026CVE publishedPublication date reported by the CVE source.
- Feb 2, 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=< 0.8.2
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.
Weakness, pattern, technique
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo