OpenC3 COSMOS: Permissions Bypass Provides User Access to Unassigned Administrative Actions via Script Runner Tool
CVE-2026-42088GHSA-2wvh-87g2-89hr
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (openc3 7.0.0; openc3 7.0.0-rc3), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record PYSEC-2026-2245 lists affected ranges: PyPI openc3 >=0 <7.0.0 (fixed)
VerifiedObserved Structured OSV record; not marked as GitHub-reviewed.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-2wvh-87g2-89hr lists affected ranges: RubyGems openc3 >=0 <7.0.0-rc3
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 9.6 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
- EPSS
- CVE-2026-42088: 0.34% estimated exploitation activity in the next 30 days; percentile 27.69 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Vulnerability Type: Execution with Unnecessary Privileges Attack type: Authenticated remote Impact: Data disclosure/manipulation, privilege escalation Affected components: The following docker images: • Openc3inc/openc3-COSMOS-script-runner-api The Script Runner widget allows users to execute Python and Ruby scripts directly from the openc3-COSMOS-script-runner-api container. Because all the docker containers share a network, users can execute specially crafted scripts to bypass the API permissions check and perform administrative actions, including reading and modifying data inside the Redis database, which can be used to read secrets and change COSMOS settings, as well as read and write to the buckets service, which holds configuration, log, and plugin files. These actions are normally only available from the Admin Console or with administrative privileges. Any user with permission to create and run scripts can connect to any service in the docker network. <img width="940"…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-2wvh-87g2-89hr
- Revision 1 · created ·
Published from osv record PYSEC-2026-2245
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-42088 Advisory: OpenC3 COSMOS: Permissions Bypass Provides User Access to Unassigned Administrative Actions via Script Runner Tool IDs: CVE-2026-42088, GHSA-2wvh-87g2-89hr Record: https://patchnext.com/advisories/cve-2026-42088 (revision 2, source checked 26 Oct 2026, 15:51 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Critical (CVSS 9.6) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: openc3 7.0.0; openc3 7.0.0-rc3. A vendor fix does not mean a deployment is fixed. ## Affected components - PyPI openc3: affected < 7.0.0; fixed in 7.0.0 - RubyGems openc3: affected < 7.0.0-rc3; fixed in 7.0.0-rc3 ## Suggested inspection (read-only) - `python -m pip show openc3`: prints the installed version. Run with the environment that serves production active. - RubyGems openc3: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on openc3. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/PYSEC-2026-2245 (OSV record PYSEC-2026-2245 lists affected ranges: PyPI openc3 >=0 <7.0.0 (fixed)) - Verified: https://github.com/advisories/GHSA-2wvh-87g2-89hr (GitHub-reviewed advisory GHSA-2wvh-87g2-89hr lists affected ranges: RubyGems openc3 >=0 <7.0.0-rc3) Commands are suggestions: review each one before running it.
Loading voting…