In Open Object Rexx (ooRexx) before 5.2.0, RXAPI relies on a world-writable /tmp file unless XDG_RUNTIME_DIR is set
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
|
AI-suggested
Users should set the environment variable XDG_RUNTIME_DIR to avoid reliance on the world-writable /tmp file. Additionally, restricting local user access and monitoring for unauthorized local activity may reduce risk until an official fix is available.
Description
Open Object Rexx (ooRexx) versions before 5.2.0 have a vulnerability where RXAPI uses a world-writable /tmp file unless the environment variable XDG_RUNTIME_DIR is set. This allows any local user to communicate with RXAPI, potentially injecting a macro that a REXX script will execute.