# CVE-2026-130327: Misconfiguration in ooRexx

> Any local user can inject macros via a world-writable /tmp file used by ooRexx RXAPI, executing code in REXX scripts.

- **Severity:** Critical 9.3 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **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 available:** No
- **Published:** 16 Nov 2026
- **Updated:** 18 Nov 2026
- **Also known as:** GHSA-2hjp-rcpc-66v4

## What is CVE-2026-130327?

CVE-2026-130327 is a critical insecure configuration 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 relies on a world-writable /tmp file unless XDG_RUNTIME_DIR is set, or localhost TCP port 10010, allowing RXAPI communication by any local user, e.g., for injection of a macro that will be executed by a REXX script.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2026-130327?

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


## How do I fix CVE-2026-130327?

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

## Is CVE-2026-130327 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-130327 and fix it if it is affected.

What it is: CVE-2026-130327 is a critical insecure configuration 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.
Exploitation: There is no known exploitation of CVE-2026-130327 in the wild and no public exploit code.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

Affected product: Open Object Rexx ooRexx. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-130327/ (Markdown: https://insights.sbomify.com/CVE-2026-130327/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-130327
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-130327
- OSV: https://osv.dev/vulnerability/CVE-2026-130327

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-130327/
Summaries are generated and may contain mistakes; the official description above is the record.
