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.
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.
Users should make sure table names used to configure CocoIndex targets are valid, regardless of this fix. Which means
{
"cwe_ids": [
"CWE-89"
],
"github_reviewed": true,
"github_reviewed_at": "2026-03-02T20:27:48Z",
"nvd_published_at": "2026-03-06T07:15:58Z",
"severity": "HIGH"
}