CVE-2026-130320 Memory corruption in ooRexx

Critical 9.3 Published Updated

Crafted messages to the ooRexx RXAPI can trigger a heap overflow and possibly execute arbitrary code; operators of ooRexx brokers should care.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Local or same network only
Victim action needed
Not needed
Harmful if only installed
No
Needs a specific call
No
Fix
None listed

What is CVE-2026-130320?

CVE-2026-130320 is a critical memory corruption vulnerability in Open Object Rexx ooRexx, published on 16 Nov 2026. It can only be exploited from the same machine or local network, with no action from the victim.

Official description

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.

Weakness: CWE-122

Which versions are affected by CVE-2026-130320?

An affected version is exposed as installed. No special setting or call is needed.

How do I fix CVE-2026-130320?

No fix has been published for CVE-2026-130320 yet. Limit exposure of the affected software until one is available.

Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.

Is CVE-2026-130320 being exploited?

There is no known exploitation of CVE-2026-130320 in the wild and no public exploit code.

Sources

Also known as GHSA-mhgw-w642-wmq2.

Is CVE-2026-130320 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free