SQL Injection in cocoindex (CVE-2026-28438)
Summary
SQL injection in cocoindex (CVE-2026-28438). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.3.34 or later.
Original description
The description as published by the source.
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.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-28438 has been found in cocoindex.
Risk of unauthorized operations or information disclosure.
What to do: upgrade cocoindex to 0.3.34 or later.
If unsure, ask your IT team or search "cocoindex CVE-2026-28438" on the vendor's site.
CVE-2026-28438 (cocoindex) — CWE-89
Patched: 0.3.34 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
SQL injection (CWE-89) exists in cocoindex.
Check the vendor advisory for the affected versions of cocoindex.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.3.34.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'cocoindex' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'cocoindex' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
cocoindexを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade cocoindex to 0.3.34ステージング環境で 0.3.34 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com