CVE-2026-42084: OpenC3 COSMOS: Hijacked session token can be used to reset password for persistence
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.
Published Apr 22, 2026 · Updated May 29, 2026
Affected packages
openc3
- Ecosystem
- RubyGems
- Affected
- < 6.10.5
- Fixed in
- 6.10.5
- Check
bundle info openc3
openc3
- Ecosystem
- RubyGems
- Affected
- >= 7.0.0.pre.rc1, < 7.0.0-rc3
- Fixed in
- 7.0.0-rc3
- Check
bundle info openc3
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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) 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
- Attacker is logged in user account with hijacked valid session token, but not knowing the actual password
- Legitimate user, as preventive action, changes his password (_password123_) using old password (_password_), that he knows, then establishes new session
- 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
Impact
Persistence of an attacker who obtained valid session token and preventing legitimate users from account access
Credited to ctrlsill.
References
- https://github.com/OpenC3/cosmos/security/advisories/GHSA-wgx6-g857-jjf7
- https://github.com/OpenC3/cosmos/commit/2e623714e3426d5ae81b6f8239d4a2a6937ef776
- https://github.com/OpenC3/cosmos/releases/tag/v6.10.5
- https://github.com/OpenC3/cosmos/releases/tag/v7.0.0-rc3
- https://nvd.nist.gov/vuln/detail/CVE-2026-42084
- https://github.com/rubysec/ruby-advisory-db/blob/master/gems/openc3/CVE-2026-42084.yml
- https://github.com/advisories/GHSA-wgx6-g857-jjf7
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More RubyGems vulnerabilities
All RubyGems entriesCVE-2026-77601
OpenC3 COSMOS: Authenticated OS command injection via the `pypi_url` setting
high8.8Sep 23, 2026CVE-2026-77602
OpenC3 COSMOS: Authenticated remote code execution via the user-writable config overlay (table definitions, cmd/tlm definitions, and script suites)
critical9.9Sep 23, 2026CVE-2026-42087
OpenC3 COSMOS has SQL Injection in QuestDB Time-Series Database
critical9.6Apr 23, 2026GHSA-2wvh-87g2-89hr
OpenC3 COSMOS: Permissions Bypass Provides User Access to Unassigned Administrative Actions via Script Runner Tool
critical9.6Apr 23, 2026CVE-2026-42085
OpenC3 COSMOS allows arbitrary writes to plugins directory via path-traversed config filenames
medium4.3Apr 22, 2026CVE-2026-42086
OpenC3 COSMOS is Vulnerable to Self-XSS Through the Command Sender
medium4.6Apr 22, 2026
