Advisory

GHSA-59g6-v3vg-f7wc

Also known as: CVE-2026-28438, PYSEC-2026-2133

Summary

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

Details

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.

Severity

High Basis: The source's own band: HIGH

Dates

Published
2026-03-02 20:27 UTC
Modified
2026-07-13 07:26 UTC

Affected packages and fixes

cocoindex

PyPI · All systems

Affected

  • introduced 0, fixed 0.3.34 (ecosystem)

Fixed versions

0.3.34

Fix

  • Fixed version 0.3.34
    pip install --upgrade cocoindex==0.3.34

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences