Quick answers
- Is CVE-2026-42085 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-42085 being exploited in the wild.
- How severe is CVE-2026-42085?
- Medium severity, with a CVSS score of 4.3, published 4 May 2026.
- Which products and versions are affected?
- Openc3 Cosmos < 6.10.5, >= 7.0.0.pre.rc1, < 7.0.0-rc3; openc3 (PyPI) ECOSYSTEM:introduced=0,fixed=6.10.5; openc3 (RubyGems) ECOSYSTEM:introduced=0,fixed=6.10.5.
- Is there a fix for CVE-2026-42085?
- Yes. openc3 (PyPI): upgrade to 6.10.5 or later; openc3 (RubyGems): upgrade to 6.10.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-42085 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-42085?
- Check whether you run Openc3 Cosmos, openc3 (PyPI) or openc3 (RubyGems) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- openc3 (PyPI): upgrade to 6.10.5 or later
pip install "openc3>=6.10.5" - openc3 (RubyGems): upgrade to 6.10.5 or later
bundle update openc3
Technical details
A path traversal vulnerability exists in the `save_tool_config()` function within `local_mode.rb`. While the application attempts to mitigate traversal by canonicalizing filenames to absolute paths, it fails to restrict writes to the specific intended subdirectory, allowing files to be saved anywhere within the broader `OPENC3_LOCAL_MODE_PATH` (the `/plugins` directory tree). An authenticated attacker with network access can use `../` sequences in configuration filenames to escape the intended directory and overwrite files belonging to other plugins. This issue is addressed in versions 6.10.5 and 7.0.0-rc3.
Affected products
- OpenC3 COSMOS < 6.10.5, >= 7.0.0.pre.rc1, < 7.0.0-rc3
Identifiers
- CVE-2026-42085
- GHSA-4jvx-93h3-f45h
- PYSEC-2026-2243
Timeline
- 2026-04-20: disclosed
- 2026-04-22: advisory: GitHub Advisory published
- 2026-05-04: other: NVD published