# CVE-2026-4229: vanna-ai vanna bigquery_vector.py remove_training_data sql injection

> Remote attackers can exploit SQL injection in the remove_training_data function of the vanna-ai library to read or modify database contents.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Mar 2026
- **Updated:** 16 Mar 2026
- **Also known as:** GHSA-6mj8-jmp2-g8q7, PYSEC-2026-3397

## What is CVE-2026-4229?

CVE-2026-4229 is a medium-severity SQL injection vulnerability in vanna-ai vanna, published on 16 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A flaw has been found in vanna-ai vanna up to 2.0.2. This impacts the function remove_training_data of the file src/vanna/legacy/google/bigquery_vector.py. This manipulation of the argument ID causes sql injection. The attack can be initiated remotely. The exploit has been published and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2026-4229?

3 open source packages ship an affected version, including vanna.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `vanna` | PyPI | All versions to 2.0.2 | None |
| `vanna` | PyPI | All versions to 2.0.2 | None |
| `vanna` | PyPI | All versions to 2.0.2 | None |

## How do I fix CVE-2026-4229?

No fix has been published for CVE-2026-4229 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-4229 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-4229 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-4229 and fix it if it is affected.

What it is: CVE-2026-4229 is a medium-severity SQL injection vulnerability in vanna-ai vanna, published on 16 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-4229 exists.

Affected packages and fixed versions:
- vanna (PyPI): affected all versions up to 2.0.2; no fix listed
- vanna (PyPI): affected all versions up to 2.0.2; no fix listed
- vanna (PyPI): affected all versions up to 2.0.2; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-4229/ (Markdown: https://insights.sbomify.com/CVE-2026-4229/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-4229
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-4229
- OSV: https://osv.dev/vulnerability/CVE-2026-4229

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-4229/
Summaries are generated and may contain mistakes; the official description above is the record.