What is the CVSS score of CVE-2026-28438?

CVE-2026-28438 has a CVSS 3.1 base score of 9.8 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.0%.

How to fix or mitigate CVE-2026-28438?

Within 24 hours: Identify all systems running CocoIndex versions prior to 0.3.34 and isolate affected environments from production if patching cannot be completed immediately. Within 7 days: Apply vendor patch to upgrade all CocoIndex instances to version 0.3.34 or later and validate functionality in a test environment before production deployment. Within 30 days: Conduct security audit of Doris database access logs to identify any potential exploitation attempts and review data access controls.

Cocoindex CVE-2026-28438

CRITICAL

SQL Injection (CWE-89)

2026-03-06 security-advisories@github.com

GHSA-59g6-v3vg-f7wc

SQLi AI / ML Cocoindex

9.8

CVSS 3.1 · GitHub Advisory

View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

Access

Provide untrusted table name to CocoIndex
Exploit

Framework passes unsanitized input to Doris connector
Execution

SQL injection in ALTER TABLE statement
Impact

Modify database schema or execute arbitrary SQL commands

Vulnerability Assessment

Weakness	CWE CWE-89 OWASP Top 10:2025 A05:2025 - Injection ASVS 5.0 V1 - Encoding and Sanitization Parameterized queries, prepared statements MITRE ATT&CK 2 techniques across 2 tactics: Initial Access, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. Sign in to read
Exploitation Conditions	CocoIndex version prior to 0.3.34 with Doris target connector enabled, receiving table name from untrusted upstream data source without input validation.
Impact	CVSS 9.8.
Exploit ScenarioDerived	SQL injection via table name.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.

Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 12, 2026

SQL injection in CocoIndex Doris connector before 0.3.34. Patch available.

Earlier versions of this analysis (1)

v1 Mar 12, 2026 - 22:06 CVSS 9.8

SQLi in CocoIndex.

RemediationAI

Update.

Affected Packages

pypi cocoindex fix: 0.3.34

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in pypi

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

CWE-89 unvalidated table name.

Know when Cocoindex gets its next vulnerability

Watch products and get an email when something new is published
Check this CVE against your own stack and servers
Exploit and PoC references, threat intelligence from 22 sources

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

GitHub Advisory PRIMARY 9.8 CRITICAL

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

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Patch released

Mar 10, 2026 - 19:47 nvd

Patch available

CVE Published

Mar 06, 2026 - 07:15 nvd

CRITICAL 9.8

DescriptionGitHub Advisory

CocoIndex is a data transformation framework for AI. Prior to version 0.3.34, the Doris target connector didn't verify the configured table name before creating some SQL statements (ALTER TABLE). So, in the application code, if the table name is provided by an untrusted upstream, it expose vulnerability to SQL injection when target schema change. This issue has been patched in version 0.3.34.

Executive ViewAI

Why It Matters

A critical vulnerability in CocoIndex versions prior to 0.3.34 allows unauthenticated attackers to execute arbitrary SQL commands through improper table name validation in the Doris connector, potentially enabling complete database compromise. Organizations using CocoIndex for data transformation should prioritize immediate patching to prevent unauthorized data access, modification, or destruction.

Business Impact: Severe

Compensating Controls

Apply vendor patch. If immediate patching is impossible: (1) Restrict network access to CocoIndex and Doris database to authorized users only via firewall rules, (2) Disable or restrict the Doris target connector functionality until patching is complete, (3) Implement database-level monitoring and alerting for unauthorized ALTER TABLE commands, (4) Enforce read-only access policies where possible until patch deployment.

Threat Intelligence Overview

EPSS Score

0.0%

Top 88% exploitable

Data Quality

4 sources

Confidence: Medium

NVD

CVE.org

EPSS

GitHub

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue

Severity CRITICAL

CISA KEV No

Public POC No

EPSS 0.0%

Patch available Yes

Active threat No

Deciding rule

CRITICAL severity

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.