CVE-2025-28388: cosmos · n/a
Affects cosmosSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical : upgrade to 6.0.2 as a priority.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 48% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 6.0.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 13 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Upgrade openc3/cosmos to 6.0.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubopenc3/cosmospkg:github/openc3/cosmosOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Organizations should immediately upgrade OpenC3 COSMOS to version 6.0.2 or later, where the hardcoded credentials issue is resolved. If immediate patching is not feasible, implement network segmentation to isolate affected systems from untrusted networks and restrict access to management interfaces. Conduct thorough audits to detect any unauthorized access or use of the hardcoded credentials. Deploy intrusion detection and prevention systems tuned to detect anomalous authentication attempts related to the service account. Enforce strict credential management policies and rotate any credentials associated with the service account if possible. Monitor logs for suspicious activity and establish incident response procedures tailored to operational technology environments. Engage with the vendor for official patches and guidance, and consider applying application-layer firewalls or access control lists to limit exposure. Finally, raise awareness among operational staff about the risks and signs of exploitation related to this vulnerability.
Description
OpenC3 COSMOS before v6.0.2 was discovered to contain hardcoded credentials for the Service Account.
References
- openc3.com (opens in a new tab)
- visionspace.com/openc3-cosmos-a-security-assessment-of-an-open-source-mission-framework/ (opens in a new tab)
- github.com/OpenC3/cosmos/releases/tag/v6.0.2 (opens in a new tab)
- github.com/OpenC3/cosmos/pull/1816 (opens in a new tab)
- github.com/OpenC3/cosmos/pull/1816/commits/195974a019f375f7c5a35f48e4151babb40649ac (opens in a new tab)