Open Object Rexx ooRexx remote code execution via heap overflow in RXAPI
- Exploited
- No known exploitation
- Fix
- Fixed in 5.2.0
- Who is exposed
- Specific setups only
Summary
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.
What to do
Upgrade to a fixed version: 5.2.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-130320 (In Open Object Rexx (ooRexx) before 5.2.0, RXAPI mishandles nameArg and userid bounds checking, possibly leading to arbitrary code…), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-130320 (entry last updated 2026-11-17):
Affected:
- Open Object Rexx ooRexx: from 4.0.0, fixed in 5.2.0
Fixed versions: 5.2.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, no login, no user action.
CISA KEV: CVE-2026-130320 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130320 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://sourceforge.net/p/oorexx/code-0/12916/
- https://sourceforge.net/p/oorexx/bugs/1982/
- https://www.cve.org/CVERecord?id=CVE-2026-130320
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-130320
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130320"}.Affected versions
- Open Object Rexx ooRexxFrom 4.0.0 · fixed in 5.2.0
cve.now Index
- Exploitation0/40No signal
- Exposure5/25Specific setups only
- Reach?/20Unknown. No tracked technology or package matched
- Severity10/10CVSS 9.3, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 25 if CISA's SSVC rates it automatable
Timeline
- CVE published
- First seen by cve.now1 day
- Posted on X by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Public exploit activity
- EPSS: 0.13%
- Posted on X by cve.now Nov 17
Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.
Evidence 4
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130320 |
| Record | NVD · CVE-2026-130320 |
| Write-ups 1Establishes: Technical detail and context. | |
| Report | sourceforge.net · p/oorexx/bugs/1982 |
| Other links 1 | |
| Patch | sourceforge.net · p/oorexx/code-0/12916 |
Questions about CVE-2026-130320
Is CVE-2026-130320 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-130320?
ooRexx: from 4.0.0 before 5.2.0.
Source: cve.now feed data
How do I fix CVE-2026-130320?
Upgrade to ooRexx 5.2.0 or later, which is the fixed version listed for this vulnerability.
Source: cve.org
Related
- CVE-2026-130327In Open Object Rexx (ooRexx) before 5.2.0, RXAPI relies on a world-writable /tmp file unless XDG_RUNTIME_DIR is set, or localhost TCP port…
- CVE-2026-130290In Open Object Rexx (ooRexx) before 5.2.0, RXAPI has a heap buffer over-read in a QueueManager DataQueue::addmethod.
- CVE-2026-19707Heap out-of-bounds write in the Smart Form Protection HTML entity decoder
- CVE-2026-134052Open Robotics RViz fillIndexBuffer Heap-based Buffer Overflow Remote Code Execution Vulnerability
- CVE-2026-62257HTSlib: Heap read and write overflow in HTSlib CRAM 4.0 decoder
- CVE-2026-63390HTSlib: Heap buffer overflow in BCF reader due to improper validation of input.
No corrections so far. Something wrong on this page? Report an error.