CVE-2026-130290: In Open Object Rexx (ooRexx) before 5.2.0, RXAPI has a heap buffer over-read in a QueueManager
Source GCVE Database
Not known to be exploited · CVSS 7.9 High : upgrade to 5.2.0 soon.
Data as of 17 Nov 2026, 01:49 UTC
Thin evidence
One scorer or none| CNA (mitre) | CVSS 3.1 | 7.9 |
|---|
- Patch
- Available – fixed in 5.2.0
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:LExploitation evidence
Disclosed: evidence found.
CVE published 16 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Upgrade ooRexx to 5.2.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Open Object RexxooRexx | Affected
| Fixed in
|
AI-suggested
If you cannot patch yet, avoid exposing the vulnerable RXAPI QueueManager interfaces to untrusted clients or restrict access to trusted users only.
Description
Open Object Rexx (ooRexx) versions before 5.2.0 contain a heap buffer over-read vulnerability in the RXAPI component's QueueManager DataQueue::add method. The issue arises because the code trusts the client-supplied message.parameter1 value as the size for copying data from a heap buffer, which can lead to reading beyond the buffer boundary. An attacker can exploit this by sending a large parameter1 value in specific queue messages, potentially causing a process crash.