dbcve.org
CWE-95Weakness · CWE-95

CVE-2025-68271

CRITICAL · 10.0 CVSS v3.1 Published 2026-01-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 provides the functionality needed to send commands to and receive data from one or more embedded systems. From 5.0.0 to 6.10.1, OpenC3 COSMOS contains a critical remote code execution vulnerability reachable through the JSON-RPC API. When a JSON-RPC request uses the string form of certain APIs, attacker-controlled parameter text is parsed into values using String#convert_to_value. For array-like inputs, convert_to_value executes eval(). Because the cmd code path parses the command string before calling authorize(), an unauthenticated attacker can trigger Ruby code execution even though the request ultimately fails authorization (401). This vulnerability is fixed in 6.10.2.

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 5.0.0 through 6.10.1 contain a critical unauthenticated RCE vulnerability in the JSON-RPC API. The String#convert_to_value method executes eval() on array-like attacker-controlled inputs before the authorize() check occurs, allowing unauthenticated Ruby code execution despite receiving a 401 authorization failure response.

MitigationUpgrade to OpenC3 COSMOS version 6.10.2 or later to remediate this vulnerability.

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

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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. Check installed OpenC3 COSMOS version
    Locate the version file or execute 'grep -r "VERSION"' in the OpenC3 installation directory, or check the gem/npm package version if installed as a package
    Affected if Version is 5.0.0 through 6.10.1 (inclusive)
  2. Verify JSON-RPC API is exposed
    Check if the JSON-RPC endpoint is accessible on the network (typically at /api or /cosmos-api path). Inspect web server configuration for exposed API routes
    Affected if JSON-RPC API endpoint is reachable from network without authentication
  3. Identify vulnerable convert_to_value method
    Search the codebase for the String#convert_to_value method definition. In Ruby installations, look in lib directories for 'def convert_to_value' that contains eval() call
    Affected if The convert_to_value method contains eval() and is used in the JSON-RPC request handling path
  4. Confirm eval executes before authorize()
    Review the JSON-RPC request handling code flow. Trace the code path from request receipt to the convert_to_value call and check if authorization happens after this method
    Affected if Code analysis shows eval in convert_to_value executes before the authorize() check in the request lifecycle

If OpenC3 COSMOS version is between 5.0.0 and 6.10.1 AND the JSON-RPC API is network-accessible, the environment is vulnerable to unauthenticated RCE

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to OpenC3 COSMOS version 6.10.2 or later to remediate this vulnerability.

Recommended fix High confidence

Upgrade to OpenC3 COSMOS version 6.10.2

  1. 1. Backup your current OpenC3 COSMOS installation and all associated data
  2. 2. Consult the official OpenC3 upgrade documentation for migrating from your current version to 6.10.2
  3. 3. Download OpenC3 COSMOS version 6.10.2 from the official source
  4. 4. Test the upgrade in a non-production environment first
  5. 5. Deploy version 6.10.2 to production after successful testing
  6. 6. Verify the installation and confirm the JSON-RPC API functions correctly
  7. 7. Confirm the vulnerability is no longer exploitable
Caveat Review release notes for 6.10.2 to check for any breaking changes or deprecations that may affect your configuration

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
14.0 hours of engineering $2,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-68271 — 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-68271 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