CVE-2026-130320: 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 mishandles nameArg and userid bounds checking, possibly leading to arbitrary code execution via crafted messages.

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 Open Object Rexx (ooRexx) to a version that resolves this vulnerability.

    Fixed in 5.2.0

Event History

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

Frequently Asked Questions

1

What access does an attacker need to exploit this issue?

The vector is local and requires no privileges or user interaction. An attacker would need a way to send crafted messages to RXAPI on the affected system.

2

Which versions are affected?

Open Object Rexx versions before 5.2.0 are affected. Upgrading to 5.2.0 or later addresses the reported bounds-checking issue.

3

What is the potential impact?

Successful exploitation may lead to arbitrary code execution. The reported severity is critical, with high confidentiality, integrity, and availability impact.

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