OOREXX · CVE-2026-130320 · Runtime
NO FIX YET · SEE WHAT TO DO
Open Object Rexx (ooRexx) before 5.2.0 mishandles bounds checking of the nameArg and userid values in RXAPI. A crafted message may let an attacker execute arbitrary code.
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.
Teams that run ooRexx and expose its RXAPI interface to messages from other processes or the network. The sources do not say which deployments receive crafted messages, so unknown beyond that.
Not affected if oorexx-5.2.0-or-later
Who cares oorexx, rexx
rexx --version or the package manager's listing5.2.0 or laterIn Open Object Rexx (ooRexx) before 5.2.0, RXAPI mishandles nameArg and userid bounds checking, possibly leading to arbitrary code execution via crafted messages.
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.