What is the severity of CVE-2026-28438?

CVE-2026-28438 has a CVSS v3 score of 0, which is classified as Low severity.

Is there an exploit available for CVE-2026-28438?

No known public exploits are currently available for CVE-2026-28438.

Is there a patch available for CVE-2026-28438?

Yes, patches are available for CVE-2026-28438. Check the vendor advisories for update instructions.

CVE-2026-28438

Q: What is CVE-2026-28438?

### Impact 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. ### Patches Yes, it's fixed in cocoindex 0.3.34: we start to validate table names passed to Doris target at entry point and error out immediately if it's not a valid identifier. ### Workarounds Users should make sure table names used to configure CocoIndex targets are valid, regardless of this fix. Which means - The table name comes from a trusted source (e.g. for most cases it's just a fixed string literal). - Even if it comes from an untrusted source (e.g. provided by end user), it should be validated before using it to configure the Doris target for CocoIndex.

Published: March 10, 2026

Last updated:16 hours ago (March 10, 2026)

Exploit: NoZero-day: NoPatch: YesTrend: Neutral

TL;DR

Updated March 10, 2026

CVE-2026-28438 is a low severity vulnerability with a CVSS score of 0.0. No known exploits currently, and patches are available.

Key Points

1Low severity (CVSS 0.0/10)
2No known public exploits
3Vendor patches are available

Severity Scores

CVSS v30.0

CVSS v20.0

Priority Score0.0

EPSS Score0.0

None

Exploitation LikelihoodMinimal

0.00%EPSS

Very low probability of exploitation

Monitor and patch as resources allow

0.00%

EPSS

0.0

CVSS

Exploit

Yes

Patch

Low Priority

no major risk factors

EPSS predicts the probability of exploitation in the next 30 days based on real-world threat data, complementing CVSS severity scores with actual risk assessment.

Description

Impact

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.

Patches

Yes, it's fixed in cocoindex 0.3.34: we start to validate table names passed to Doris target at entry point and error out immediately if it's not a valid identifier.

Workarounds

Users should make sure table names used to configure CocoIndex targets are valid, regardless of this fix. Which means

The table name comes from a trusted source (e.g. for most cases it's just a fixed string literal).
Even if it comes from an untrusted source (e.g. provided by end user), it should be validated before using it to configure the Doris target for CocoIndex.

CVSS v3 Breakdown

Attack Vector:-

Attack Complexity:-

Privileges Required:-

User Interaction:-

Scope:-

Confidentiality:-

Integrity:-

Availability:-

Patch References

Github.com

Trend Analysis

Neutral

Advisories

GitHub Advisory NVD

Cite This Page

APA Format

Strobes VI. (2026). CVE-2026-28438 - CVE Details and Analysis. Strobes VI. Retrieved March 10, 2026, from https://vi.strobes.co/cve/CVE-2026-28438

Quick copy link + title

Please cite this page when referencing data from Strobes VI. Proper attribution helps support our vulnerability intelligence research.