CVE-2026-130327: Critical severity Open Object Rexx Open Object Rexx (ooRexx) vulnerability
In Open Object Rexx (ooRexx) before 5.2.0, RXAPI relies on a world-writable /tmp file unless XDGRUNTIMEDIR is set, or localhost TCP port 10010, allowing RXAPI communication by any local user, e.g., for injection of a macro that will be executed by a REXX script.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 5.2.0
Event History
Frequently Asked Questions
Who can exploit this issue?
Any local user who can communicate with RXAPI may be able to inject a macro for execution by a REXX script. No privileges or user interaction are required according to the supplied vector.
Are default deployments affected?
RXAPI is affected when it relies on its world-writable /tmp file, which occurs unless XDG_RUNTIME_DIR is set. Configurations using localhost TCP port 10010 for RXAPI communication are also affected.
What can be done before upgrading?
Set XDG_RUNTIME_DIR so RXAPI does not rely on the world-writable /tmp file. Also review whether RXAPI is using localhost TCP port 10010 and restrict local access where possible.
How can I determine whether a system is exposed?
Check whether the installed ooRexx version is earlier than 5.2.0, whether XDG_RUNTIME_DIR is unset for RXAPI, and whether RXAPI communicates through localhost TCP port 10010.