What is CVE-2026-28438?

CVE-2026-28438 is a high-severity SQL injection vulnerability in cocoindex (pip), affecting versions < 0.3.34. It is fixed in 0.3.34. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.

Which versions of cocoindex are affected by CVE-2026-28438?

cocoindex (pip) versions < 0.3.34 is affected.

Is there a fix for CVE-2026-28438?

Yes. CVE-2026-28438 is fixed in 0.3.34. Upgrade to this version or later.

Is CVE-2026-28438 exploitable, and should I be worried?

Whether CVE-2026-28438 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-28438 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-28438?

Upgrade cocoindex to 0.3.34 or later.

CVE-2026-28438 in cocoindex

Q: Which versions of cocoindex are affected by CVE-2026-28438?

cocoindex (pip) versions < 0.3.34 is affected.

Q: Is there a fix for CVE-2026-28438?

Yes. CVE-2026-28438 is fixed in 0.3.34. Upgrade to this version or later.

Q: Is CVE-2026-28438 exploitable, and should I be worried?

Whether CVE-2026-28438 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-28438 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-28438?

Upgrade cocoindex to 0.3.34 or later.

Summary

CocoIndex Doris target connector didn't verify table name when constructing ALTER TABLE statements

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.

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.

Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access. Typical impact: data disclosure or modification.

Affected versions

cocoindex (< 0.3.34)

Security releases

cocoindex → 0.3.34 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

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.

Frequently Asked Questions

What is CVE-2026-28438? CVE-2026-28438 is a high-severity SQL injection vulnerability in cocoindex (pip), affecting versions < 0.3.34. It is fixed in 0.3.34. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.
Which versions of cocoindex are affected by CVE-2026-28438? cocoindex (pip) versions < 0.3.34 is affected.
Is there a fix for CVE-2026-28438? Yes. CVE-2026-28438 is fixed in 0.3.34. Upgrade to this version or later.
Is CVE-2026-28438 exploitable, and should I be worried? Whether CVE-2026-28438 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-28438 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-28438? Upgrade cocoindex to 0.3.34 or later.