CVE-2025-28388 json
OpenC3 COSMOS before v6.0.2 was discovered to contain hardcoded credentials for the Service Account.
published 2025-06-13 16 mo ago modified 2026-07-13 3 mo ago also PYSEC-2025-258 , EUVD-2025-18269
- cvss
- 9.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 49%
- public exploits
- 0
- none known
Summary
OpenC3 COSMOS before v6.0.2 was discovered to contain hardcoded credentials for the Service Account.
Patch / fix
- github.com/OpenC3/cosmos#1816 commit
- github.com/OpenC3/cosmos#1816 pull request
- github.com/OpenC3/cosmos/releases/tag/v6.0.2 release
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- total
- Assessed
- 16 mo ago
Exploit prediction
0.61% chance of exploitation in the next 30 days, higher than 49% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- visionspace.com https://visionspace.com/openc3-cosmos-a-security-assessment-of-an-open-source-mission-framework/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| OSV | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | openc3 | <=6.0.0 |
no fix listed |
Classification
- Weakness
-
- CWE-798 Use of Hard-coded Credentials
References
-
github.com
/OpenC3/cosmos/pull/1816
patch
-
github.com
/OpenC3/cosmos/pull/1816/commits/195974a019f375f7c5a35f48e4151babb40649ac
web
-
visionspace.com
/openc3-cosmos-a-security-assessment-of-an-open-source-mission-framework/
exploit, mitigation, third-party-advisory, evidence
-
openc3.com
/
product, web
-
github.com
/OpenC3/cosmos/releases/tag/v6.0.2
web
Sources
- CVE List CVE-2025-28388
- NVD CVE-2025-28388
- OSV PYSEC-2025-258
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.