CVE-2026-42084: OpenC3 COSMOS Hijacked Session Token Can Be Vulnerability

HIGH
Advisory Identifier: GHSA-wgx6-g857-jjf7
CVSS 8.1
CWE-620
Published
Advisory Summary

CVE-2026-42084 is a HIGH (CVSS 8.1) hijacked session token can be vulnerability (CWE-620: Unverified Password Change) affecting OpenC3 COSMOS libraries in the RubyGems ecosystem. The issue involves hijacked session token can be used to reset password for persistence. Remediation is available by upgrading affected packages to version 6.10.5, 7.0.0-rc3.

CVE-2026-42084 at a Glance

CVE Identifier CVE-2026-42084
GHSA Identifier GHSA-wgx6-g857-jjf7
Severity HIGH
CVSS v3.1 Base Score 8.1
CWE Classification CWE-620: Unverified Password Change
Affected Product OpenC3 COSMOS
Package Ecosystem RubyGems
Published Date
Last Updated

Security Impact

CVSS: 8.1

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability None (A:N)

How to Fix CVE-2026-42084

To remediate this vulnerability, upgrade all affected OpenC3 COSMOS dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

openc3 fixed: 6.10.5
Upgrade openc3 to 6.10.5
openc3 fixed: 7.0.0-rc3
Upgrade openc3 to 7.0.0-rc3
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for openc3

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-42084, inspect your project dependencies for OpenC3 COSMOS:

inspect dependencies for openc3

Analyze the terminal output to locate any version of OpenC3 COSMOS in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 6.10.5), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-620: Unverified Password Change, where when setting a new password for a user, the product does not require knowledge of the original password, or using another form of authentication. In OpenC3 COSMOS, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary The OpenC3 password change functionality allows a user to change their password without providing the old password, by accepting a valid session token instead. In assumed breach scenarios, this behaviour can be exploited by an attacker who has already obtained a valid session token, to gain persistence in hijacked account (including admin) and prevent legitimate users from accessing the account. ### Details The design flaw in authentication model ([authentication.rb](https://github.com/OpenC3/cosmos/blob/397abec0d57972881a2e8dc10902d0dce9c27f42/openc3/lib/openc3/utilities/authentication.rb)) allows for interchangeable use of password and session tokens for user authentication As old tokens are not revoked upon password reset, an attacker who has obtained a valid session token can continue to authenticate and change the account’s password even after the victim resets it, thereby maintaining persistent control over the compromised account. ### PoC 1. Attacker is logged in user account with hijacked valid session token, but not knowing the actual password 2. Legitimate user, as preventive action, changes his password (_password123_) using old password (_password_), that he knows, then establishes new session 3. Attacker issues another password change request (in web proxy like Burp) supplying his still valid token as _old_password_, changing it to attacker-password, from this point preventing any other legitimate users from accessing account <img width="912" height="479" alt="image" src="https://github.com/user-attachments/assets/d27b5980-0326-40f8-bb39-657d7b1c95a0" /> <img width="923" height="423" alt="image" src="https://github.com/user-attachments/assets/060d9fe1-637e-4a2d-9142-76612984ea28" /> ### Impact Persistence of an attacker who obtained valid session token and preventing legitimate users from account access

CVE-2026-42084 Affected OpenC3 COSMOS Versions

2 component(s)
Fixed Versions:
6.10.57.0.0-rc3
Product / Package Ecosystem Affected Versions Fixed Version
openc3
RubyGems
< 6.10.5
6.10.5
openc3
RubyGems
≥ 7.0.0.pre.rc1
< 7.0.0-rc3
7.0.0-rc3

References

Frequently Asked Questions

What is CVE-2026-42084?
CVE-2026-42084 is a security vulnerability in OpenC3 COSMOS involving Hijacked session token can be used to reset password for persistence under CWE-620: Unverified Password Change.
Which OpenC3 COSMOS versions are affected?
Affected versions include releases prior to 6.10.5, 7.0.0-rc3 across affected packages: openc3.
What version fixes CVE-2026-42084?
Upgrading to 6.10.5, 7.0.0-rc3 (or the latest patched release for your respective branch) resolves the vulnerability.
Is openc3 affected?
Yes, openc3 is affected in releases prior to 6.10.5, 7.0.0-rc3. Upgrade your dependency to 6.10.5, 7.0.0-rc3 or later.
What is the CVSS score of CVE-2026-42084?
CVE-2026-42084 has a CVSS v3.1 base score of 8.1 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N.
What CWE is associated with CVE-2026-42084?
CVE-2026-42084 is classified under CWE-620: Unverified Password Change (When setting a new password for a user, the product does not require knowledge of the original password, or using another form of authentication.).
How can I check RubyGems dependencies for CVE-2026-42084?
Run the dependency tree command: 'inspect dependencies for openc3'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-wgx6-g857-jjf7",
  "modified" : "2026-05-29T21:45:03Z",
  "published" : "2026-04-22T22:13:10Z",
  "aliases" : [ "CVE-2026-42084" ],
  "summary" : "OpenC3 COSMOS: Hijacked session token can be used to reset password for persistence",
  "details" : "### Summary\nThe OpenC3 password change functionality allows a user to change their password without providing the old password, by accepting a valid session token instead. In assumed breach scenarios, this behaviour can be exploited by an attacker who has already obtained a valid session token, to gain persistence in hijacked account (including admin) and prevent legitimate users from accessing the account.\n\n### Details\nThe design flaw in authentication model ([authentication.rb](https://github.com/OpenC3/cosmos/blob/397abec0d57972881a2e8dc10902d0dce9c27f42/openc3/lib/openc3/utilities/authentication.rb)) allows for interchangeable use of password and session tokens for user authentication As old tokens are not revoked upon password reset, an attacker who has obtained a valid session token can continue to authenticate and change the account’s password even after the victim resets it, thereby maintaining persistent control over the compromised account.\n\n### PoC\n1. Attacker is logged in user account with hijacked valid session token, but not knowing the actual password\n2. Legitimate user, as preventive action, changes his password (_password123_) using old password (_password_), that he knows, then establishes new session\n3. Attacker issues another password change request (in web proxy like Burp) supplying his still valid token as _old_password_, changing it to attacker-password, from this point preventing any other legitimate users from accessing account\n<img width=\"912\" height=\"479\" alt=\"image\" src=\"https://github.com/user-attachments/assets/d27b5980-0326-40f8-bb39-657d7b1c95a0\" />\n<img width=\"923\" height=\"423\" alt=\"image\" src=\"https://github.com/user-attachments/assets/060d9fe1-637e-4a2d-9142-76612984ea28\" />\n\n### Impact\nPersistence of an attacker who obtained valid session token and preventing legitimate users from account access",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "RubyGems",
      "name" : "openc3"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "6.10.5"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "RubyGems",
      "name" : "openc3"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "7.0.0.pre.rc1"
      }, {
        "fixed" : "7.0.0-rc3"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/OpenC3/cosmos/security/advisories/GHSA-wgx6-g857-jjf7"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-42084"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/OpenC3/cosmos/commit/2e623714e3426d5ae81b6f8239d4a2a6937ef776"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/OpenC3/cosmos"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/OpenC3/cosmos/releases/tag/v6.10.5"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/OpenC3/cosmos/releases/tag/v7.0.0-rc3"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/rubysec/ruby-advisory-db/blob/master/gems/openc3/CVE-2026-42084.yml"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-620" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-04-22T22:13:10Z",
    "nvd_published_at" : "2026-05-04T18:16:30Z"
  }
}