CVE-2026-130290: High severity Open Object Rexx Open Object Rexx vulnerability
In Open Object Rexx (ooRexx) before 5.2.0, RXAPI has a heap buffer over-read in a QueueManager DataQueue::addmethod. In particular, the code blindly trusts the message.parameter1 value provided by the client as the size used to fill the data from the queueData heap buffer. An attacker sends a large parameter1 value in an ADDTOSESSIONQUEUE or ADDTONAMEDQUEUE message and then retrieves data with a PULLFROMSESSIONQUEUE message. (A very large value causes a process crash.)
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 is exposed to this issue?
Systems running Open Object Rexx versions before 5.2.0 with the RXAPI service reachable by a local attacker are exposed. The attack vector is local and requires no privileges or user interaction.
What must an attacker do to exploit it?
An attacker must send an ADD_TO_SESSION_QUEUE or ADD_TO_NAMED_QUEUE message with a large parameter1 value, then retrieve the queued data using a PULL_FROM_SESSION_QUEUE message. RXAPI trusts parameter1 as the size for reading from its queueData heap buffer.
What is the likely impact?
The flaw can disclose memory contents because it reads beyond the heap buffer. A very large parameter1 value can also crash the affected process.
How can I tell whether I am affected?
You are affected if RXAPI is in use on an Open Object Rexx installation older than 5.2.0. The supplied information does not provide a configuration-based indicator beyond the presence of the vulnerable RXAPI component.