CVE-2026-22780VulnerabilityPublished 2 Feb 2026

CVE-2026-22780: rizinorg rizin · Unthrottled Resource Allocation

Affects rizinorg rizinSource CVE Database V5

Not known to be exploited · CVSS 4.4 Medium : upgrade to 0.8.2 when convenient.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score

4.4Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 0.8.2

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 2 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade rizin and rizinorg/rizin to 0.8.2.

Affected software

Product	Affected	Fixed in
rizinorgrizin	Affected <0.8.2	Fixed in 0.8.2
GitHubrizinorg/rizin`pkg:github/rizinorg/rizin`Other threats	Affected <0.8.2	Fixed in 0.8.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

The primary mitigation is to upgrade rizin to version 0.8.2 or later, where the vulnerability has been addressed. Organizations should enforce strict version control and patch management policies for security tools like rizin. Additionally, limit the exposure of rizin to untrusted or unauthenticated users to reduce the risk of processing malicious Mach-O files. Implement file integrity monitoring and scanning for suspicious or malformed Mach-O files before analysis. Educate users and analysts on the risks of opening unverified binaries within reverse engineering tools. Employ sandboxing or containerization for running rizin to contain potential crashes or memory corruption effects. Regularly audit and monitor the use of reverse engineering tools to detect anomalous activities. Finally, maintain up-to-date backups and incident response plans to recover quickly from potential denial of service or integrity incidents caused by exploitation attempts.

Description

CVE-2026-22780 is a medium severity heap overflow vulnerability in rizin versions prior to 0.8.2. It occurs when rizin parses a malicious Mach-O file containing bogus entries in the dyld chained segments, leading to allocation of resources without proper limits or throttling. Exploitation requires local access and user interaction, with no privileges needed, and can result in partial integrity and availability impacts. The vulnerability has not been observed exploited in the wild and was fixed in version 0.8.2. European organizations using rizin for reverse engineering or malware analysis should update promptly to mitigate risks. The threat primarily affects UNIX-like environments where rizin is deployed, with higher relevance in countries with strong cybersecurity research and software development sectors.

Impact

For European organizations, the impact of CVE-2026-22780 depends largely on the use of rizin within their security or development workflows. Organizations involved in reverse engineering, malware analysis, or software security research that utilize rizin on UNIX-like systems could face risks of application crashes or integrity issues if malicious Mach-O files are processed. This could disrupt analysis workflows or lead to denial of service conditions. While the vulnerability does not directly expose sensitive data or allow remote code execution, the potential for integrity compromise and availability disruption could hinder incident response or forensic investigations. The threat is more pronounced in sectors with advanced cybersecurity capabilities, such as financial services, telecommunications, and government agencies, where reverse engineering tools are commonly used. Additionally, organizations handling macOS binaries or cross-platform software development might be more exposed. Since exploitation requires local access and user interaction, the risk from external attackers is limited, but insider threats or targeted attacks involving crafted Mach-O files remain a concern.

CWE-770Allocation of Resources Without Limits or Throttling (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #25
The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.
Requirements
Clearly specify the minimum and maximum expectations for capabilities, and dictate which behaviors are acceptable when resource allocation reaches limits.
Architecture and Design
Limit the amount of resources that are accessible to unprivileged users. Set per-user limits for resources. Allow the system administrator to define these limits. Be careful to avoid CWE-410.
Architecture and Design
Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
OWASP ASVS 4.0.3
V8.1.4 (opens in a new tab)
V13.4.1 (opens in a new tab)
V11.1.4 (opens in a new tab)
Attack patterns
XML Ping of the Death (opens in a new tab)
Exponential Data Expansion (opens in a new tab)
Serialized Data Parameter Blowup (opens in a new tab)
Serialized Data with Nested Payloads (opens in a new tab)
Oversized Serialized Data Payloads (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Feb 2026, 11:09 UTC

WeaknessesCWE-770

Technical details

References

Community reviews

Related threats