# OpenC3 COSMOS: Permissions Bypass Provides User Access to Unassigned Administrative Actions via Script Runner Tool

Advisory record · `GHSA-2wvh-87g2-89hr`

- **Identifiers:** `GHSA-2wvh-87g2-89hr` · `CVE-2026-42088` · `PYSEC-2026-2245`
- **State:** Confirmed
- **Severity:** CVSS 9.6 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-250](https://cwe.mitre.org/data/definitions/250.html)
- **Tags:** [Privilege escalation](https://agentprime.io/advisories/tag/privilege-escalation.md)
- **Published:** 23 Apr 2026
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 23 Apr 2026, 14:17 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 9.6: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `openc3` (RubyGems): affected `<7.0.0-rc3`; fixed in `7.0.0-rc3`

## Machine-written summary

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

> OpenC3 COSMOS (the openc3 RubyGems package) versions before 7.0.0-rc3 are affected. An authenticated user who can create and run scripts can run crafted scripts in the Script Runner container to reach other services on the Docker network, such as Redis and the buckets service. This lets them read secrets and modify settings or files that are normally limited to administrators. Upgrade to openc3 7.0.0-rc3 or later. The source suggests limiting the Script Runner API's permissions so lower-privileged users cannot perform administrative actions.

Written 6 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 9.6 Critical, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0034, the 27th percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:04 UTC: First seen by agentprime
- 31 Oct 2026, 15:04 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/PYSEC-2026-2245)

## Sources

- [GitHub Advisory Database: GHSA-2wvh-87g2-89hr](https://github.com/advisories/GHSA-2wvh-87g2-89hr)
- [OSV: GHSA-2wvh-87g2-89hr](https://osv.dev/vulnerability/GHSA-2wvh-87g2-89hr)
- <https://github.com/OpenC3/cosmos/security/advisories/GHSA-2wvh-87g2-89hr>
- <https://github.com/OpenC3/cosmos>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-2wvh-87g2-89hr>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-2wvh-87g2-89hr/>. Everything for agents: <https://agentprime.io/llms.txt>.