dbcve.org
CosmosApplication · Openc3

CVE-2025-28388

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-13
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
OpenC3 COSMOS before v6.0.2 was discovered to contain hardcoded credentials for the Service Account.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

OpenC3 COSMOS versions before v6.0.2 contain hardcoded credentials embedded in the software for the Service Account. This critical vulnerability (CVSS 9.8) allows unauthenticated remote attackers to gain unauthorized access to the Service Account using the exposed credentials, potentially achieving complete compromise of confidentiality, integrity, and availability.

MitigationUpgrade to OpenC3 COSMOS v6.0.2 or later. Additionally, audit all deployments to identify and rotate any instances where the hardcoded credentials may have been exposed or exfiltrated, and implement proper secret management (e.g., environment variables, secrets vault) instead of embedded credentials.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CosmosApplication
Affected:= 6.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify OpenC3 COSMOS installed version
    Check the version of OpenC3 COSMOS installed in your environment. This can typically be done by running 'openc3 --version' or checking the version file in the installation directory, or checking the gem version if installed as a Ruby gem.
    Affected if The installed version is exactly 6.0.0
  2. Search for hardcoded credentials in configuration files
    Search the OpenC3 COSMOS installation directory for files containing hardcoded credentials. Look for config files, yaml files, or properties files that may contain plaintext passwords. Use grep or similar tools to search for patterns like 'password', 'secret', 'credential' in the codebase.
    Affected if Hardcoded credentials are found in configuration files within the OpenC3 COSMOS installation
  3. Inspect Service Account configuration
    Locate and examine the Service Account configuration in OpenC3 COSMOS. Check the configuration files related to user authentication and service accounts for any hardcoded username/password combinations.
    Affected if The Service Account is configured with hardcoded credentials instead of using environment variables or a secrets manager

Your environment is affected if OpenC3 COSMOS version 6.0.0 is deployed AND hardcoded credentials for the Service Account are present in the configuration.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade to OpenC3 COSMOS v6.0.2 or later. Additionally, audit all deployments to identify and rotate any instances where the hardcoded credentials may have been exposed or exfiltrated, and implement proper secret management (e.g., environment variables, secrets vault) instead of embedded credentials.

Recommended fix Moderate confidence

v6.0.2

  1. Upgrade Cosmos from version 6.0.0 to version 6.0.2 or later as specified in the official release notes
  2. After upgrading, rotate/change the Service Account credentials that were hardcoded in the affected version
  3. Verify the new credentials are properly configured and the application functions correctly after upgrade
  4. Consult the official OpenC3 Cosmos upgrade documentation for any additional migration steps
Caveat Review release notes for v6.0.1 and v6.0.2 to check for any breaking changes between your current version and the fixed release

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cosmos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-28388 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-28388 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data