CVE-2026-130290 · Runtime
NO FIX YET · SEE WHAT TO DO
Open Object Rexx before 5.2.0 trusts a client-supplied size value when filling data from a queue heap buffer, so a crafted ADD_TO_SESSION_QUEUE or ADD_TO_NAMED_QUEUE message followed by PULL_FROM_SESSION_QUEUE can read past the buffer. An attacker can read adjacent process memory, and a very large value crashes the process.
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.
No product ranges from the sources yet.
Not affected if local-only, rxapi-unused
Who cares oorexx, rxapi
rexx --version or the package manager, and compare it to the fixed version.5.2.0 or later.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 ADD_TO_SESSION_QUEUE or ADD_TO_NAMED_QUEUE message and then retrieves data with a PULL_FROM_SESSION_QUEUE message. (A very large value causes a process crash.)
This page as .md · .json · CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L
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.