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

CRITICAL 9.8CVE-2026-28438 · GHSA-59g6-v3vg-f7wc · PYSEC-2026-2133 · Published 06/03/2026 · updated 17/06/2026

Package	Affected versions	Patched versions
cocoindex PyPI	`< 0.3.34`	`0.3.34`
cocoindex cocoindex	`< 0.3.34`	`0.3.34`

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.

NVD description

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.

References

cocoindex-io/cocoindex security advisory · WEB
nvd.nist.gov/vuln/detail/CVE-2026-28438 · ADVISORY
cocoindex-io/cocoindex commit ba2fc4a · WEB
cocoindex-io/cocoindex · PACKAGE

Running one of these products? Scan your site to see whether it exposes a vulnerable version.

Scan my site free

Package

Affected versions

Patched versions

cocoindex

PyPI

< 0.3.34

0.3.34

cocoindex

< 0.3.34

0.3.34

Description

Impact

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.

NVD description