Is this vulnerability remotely exploitable?

It can be, depending on how COSMOS is deployed. If TSDB lookup functionality is reachable over a network interface where an attacker can control query parameters, remote exploitation is feasible.

Does an attacker need authenticated access to exploit this?

In many deployments, yes—attackers often need at least the same level of access as a user who can trigger TSDB lookups. However, if an instance exposes those endpoints without proper authentication or is integrated with untrusted systems, exploitation could occur without traditional user credentials.

What is the safest general fix pattern for this issue?

The most robust fix is to replace all string-built SQL in TSDB-related code with parameterized queries or ORM query builders, combined with strict input validation and least-privilege database credentials.

Severity:

CRITICAL RISK

(9.6)

SQL Injection (CWE-89) in OpenC3 COSMOS Time-Series Database (TSDB)

CVE-2026-42087

Published:

May 4, 2026

Status:

Received

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-918

HIGH RISK

HIGH

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

Unauthorized Access to Internal Resources via SSRF

May 6, 2026

CWE-863

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Privilege Escalation via Bypassed Access Control

May 6, 2026

Vulnerability Type

Category:

SQL Injection

CWE:

CWE-89

Impact:

Arbitrary SQL Command Execution and Data Integrity Compromise

Severity:

CRITICAL RISK

(9.6)

CVSS Version:

3.1

Vulnerability Type

Category:

SQL Injection

CWE:

CWE-89

Impact:

Arbitrary SQL Command Execution and Data Integrity Compromise

Severity:

CRITICAL RISK

(9.6)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

CodeAnt AI is an offensive and defensive security platform.

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

SOC 2 Type II certified | CodeAnt AI is independently audited and compliant with SOC 2 Type II security standards

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

SQL Injection (CWE-89) in OpenC3 COSMOS Time-Series Database (TSDB)

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

HIGH RISK

HIGH

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Ship clean & secure code faster

Ship clean & secure code faster

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal