CVE-2026-130327 · Runtime
NO FIX YET · SEE WHAT TO DO
Open Object Rexx before 5.2.0 lets RXAPI communication go through a world-writable /tmp file or localhost port 10010 when XDG_RUNTIME_DIR is unset. Any local user can inject a macro that a REXX script then executes.
first public Nov 16, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Systems that run ooRexx with RXAPI and where XDG_RUNTIME_DIR is not set, so the fallback /tmp file or localhost port 10010 is used. Any local user on such a machine can inject macros that REXX scripts execute. Systems on 5.2.0 or later, or where XDG_RUNTIME_DIR is set and the port is not exposed to other users, are not affected by this description.
Not affected if rxapi-unused, version-5.2.0-or-later, xdg-runtime-dir-set
Who cares linux, oorexx, rexx, self-hosted
rexx --version or check the installed ooRexx version against the fixed version below.XDG_RUNTIME_DIR is set for the users and services that run REXX scripts.5.2.0 or later.In Open Object Rexx (ooRexx) before 5.2.0, RXAPI relies on a world-writable /tmp file unless XDG_RUNTIME_DIR 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.
This page as .md · .json · CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.