In Open Object Rexx (ooRexx) before 5.2.0, RXAPI mishandles nameArg and userid bounds checking, possibly leading to
Source GCVE Database
Not known to be exploited · CVSS 9.3 Critical : upgrade to 5.2.0 as a priority.
Data as of 17 Nov 2026, 01:49 UTC
Thin evidence
One scorer or none| CNA (mitre) | CVSS 3.1 | 9.3 |
|---|
- Patch
- Available – fixed in 5.2.0
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 16 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 16 Nov 2026.
What to do
Upgrade ooRexx to 5.2.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Open Object RexxooRexx | Affected
| Fixed in
|
Description
Open Object Rexx (ooRexx) versions before 5.2.0 contain a vulnerability in the RXAPI component where improper bounds checking of nameArg and userid parameters can lead to arbitrary code execution. This flaw allows an attacker with local access to craft malicious messages that exploit this weakness. The vulnerability is rated critical with a high CVSS score of 9.3, indicating severe confidentiality, integrity, and availability impacts.