Skip to content

← Actionable
High, CVSS 7.5amended

OpenC3 COSMOS Vulnerable to Directory Traversal via openc3-api/tables endpoint

CVE-2025-28382GHSA-cf8v-5mrc-jv7f

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

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

  • RubyGems openc3-cosmos-tool-iframe

    Affected
    >= 6.0.0, <= 6.0.0
    Fixed in
    no fixed version recorded
  • PyPI openc3

    Affected
    <= 6.0.0
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
  • CVE-2025-28382: 0.89% estimated exploitation activity in the next 30 days; percentile 59.30 (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.

An issue in the openc3-api/tables endpoint of OpenC3 COSMOS 6.0.0 allows attackers to execute a directory traversal.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-cf8v-5mrc-jv7f

  2. Revision 1 · created ·

    Published from osv record PYSEC-2025-256

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-2025-28382

Advisory: OpenC3 COSMOS Vulnerable to Directory Traversal via openc3-api/tables endpoint
IDs: CVE-2025-28382, GHSA-cf8v-5mrc-jv7f
Record: https://patchnext.com/advisories/cve-2025-28382 (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: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- RubyGems openc3-cosmos-tool-iframe: affected >= 6.0.0, <= 6.0.0
- PyPI openc3: affected <= 6.0.0

## Suggested inspection (read-only)
- RubyGems openc3-cosmos-tool-iframe: check the installed version with your package manager.
- `python -m pip show openc3`: prints the installed version. Run with the environment that serves production active.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on openc3-cosmos-tool-iframe, 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-2025-256 (OSV record PYSEC-2025-256 lists affected ranges: PyPI openc3 >=0 <=6.0.0)
- Verified: https://github.com/advisories/GHSA-cf8v-5mrc-jv7f (GitHub-reviewed advisory GHSA-cf8v-5mrc-jv7f lists affected ranges: RubyGems openc3-cosmos-tool-iframe >=6.0.0 <=6.0.0)

Commands are suggestions: review each one before running it.

Loading voting…