CVE-2026-130327: Critical severity Open Object Rexx Open Object Rexx (ooRexx) vulnerability

Published Nov 16, 2026
·
Updated

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

1 affected component
Open Object Rexx Open Object Rexx (ooRexx)<5.2.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 5.2.0

Event History

Nov 16, 2026
CVE Published
via MITRE·10:39 PM
Data Sourced
via MITRE·10:39 PM
RemedyDescriptionSeverityWeakness

Frequently Asked Questions

1

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.

2

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.

3

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.

4

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203