NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · PyPI

CVE-2026-28438: CocoIndex Doris target connector didn't verify table name when constructing ALTER TABLE statements

highCVSS 4.0 8.0GHSA-59g6-v3vg-f7wc

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.

Published Mar 2, 2026 · Updated Mar 6, 2026

Affected packages

cocoindex

Ecosystem
PyPI
Affected
< 0.3.34
Fixed in
0.3.34
Check
pip show cocoindex

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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.

Credited to 4ur0n.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology