# Open Object Rexx ooRexx: In Open Object Rexx (ooRexx) before 5.2.0…

CVE record · `CVE-2026-130290`

- **Identifiers:** `CVE-2026-130290`
- **State:** Confirmed
- **Severity:** CVSS 7.9 High
- **Critical:** No
- **CNA:** mitre
- **Weakness (CWE):** [CWE-130](https://cwe.mitre.org/data/definitions/130.html)
- **Tags:** [CWE-130](https://agentprime.io/advisories/tag/cwe-130.md)
- **Technologies:** [Open Object Rexx ooRexx](https://agentprime.io/advisories/technology/open-object-rexx-oorexx.md)
- **Published:** 16 Nov 2026
- **Updated:** 17 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: mitre) at 16 Nov 2026, 22:12 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Open Object Rexx. Product: ooRexx.
  - affected: `4.0.0 to before 5.2.0` (semver)
  - Other versions: unaffected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Open Object Rexx (ooRexx) versions 4.0.0 before 5.2.0 are affected by a heap buffer over-read in the RXAPI QueueManager's DataQueue add method, which trusts a client-supplied size value when copying queue data. An attacker who can send ADD_TO_SESSION_QUEUE or ADD_TO_NAMED_QUEUE messages can then read heap memory beyond the buffer by retrieving data with PULL_FROM_SESSION_QUEUE, and a very large value can crash the process. The source gives no fixed version or workaround, so upgrading to 5.2.0 or later is the stated remedy only by implication; no fix is listed in the source.

Written 21 Nov 2026.

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

- 7.9 High, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L`, from CNA (mitre)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0012, the 1st percentile, on 22 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 16 Nov 2026, 22:12 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-130290)
- 16 Nov 2026, 22:18 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-130290)
- 16 Nov 2026, 22:20 UTC: First seen by agentprime

## Sources

- [CVE List: CVE-2026-130290](https://www.cve.org/CVERecord?id=CVE-2026-130290)
- [NVD: CVE-2026-130290](https://nvd.nist.gov/vuln/detail/CVE-2026-130290)

### References from the CNA

- <https://sourceforge.net/p/oorexx/bugs/1983/> (issue-tracking)
- <https://sourceforge.net/p/oorexx/code-0/12916/> (patch)

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2026-130290>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2026-130290/>. Everything for agents: <https://agentprime.io/llms.txt>.
