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%.

Which versions of AI / ML are affected by CVE-2026-28438?

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,…. A patch is available.

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.

AI / ML 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

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

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Mar 12, 2026 - 22:06 vuln.today

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.