ooRexx up to 5.1.x RXAPI nameArg/userid memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.1 | $0-$5k | 0.50+ |
Summary
A vulnerability has been found in ooRexx up to 5.1.x and classified as critical. Affected is an unknown function of the component RXAPI. The manipulation of the argument nameArg/userid leads to memory corruption. This vulnerability is traded as CVE-2026-130320. It is possible to initiate the attack remotely. There is no exploit available. The affected component should be upgraded.
Details
A vulnerability was found in ooRexx up to 5.1.x and classified as critical. This issue affects an unknown part of the component RXAPI. The manipulation of the argument nameArg/userid with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to CWE-119. The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
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.
The advisory is shared at sourceforge.net. The identification of this vulnerability is CVE-2026-130320 since 11/16/2026. The exploitation is known to be easy. The attack may be initiated remotely. Technical details are known, but no exploit is available.
Upgrading to version 5.2.0 eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.3VulDB Meta Temp Score: 8.1
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 9.3
CNA Vector (MITRE): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: ooRexx 5.2.0
Timeline
11/16/2026 Advisory disclosed11/16/2026 CVE reserved
11/16/2026 VulDB entry created
11/16/2026 VulDB entry last update
Sources
Advisory: sourceforge.netStatus: Confirmed
CNA: MITRE
CVE: CVE-2026-130320 (🔒)
GCVE (CVE): GCVE-0-2026-130320
GCVE (VulDB): GCVE-100-437909
Entry
Created: 11/16/2026 23:48Changes: 11/16/2026 23:48 (63)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.