# CVE-2026-4511: vanna-ai vanna legacy exec injection

> Remote attackers can execute arbitrary code via injection in the legacy exec function of the vanna-ai library.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Mar 2026
- **Updated:** 23 Mar 2026
- **Also known as:** GHSA-7ggr-c9vj-59r7

## What is CVE-2026-4511?

CVE-2026-4511 is a medium-severity code injection vulnerability in vanna-ai vanna, published on 21 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A security vulnerability has been detected in vanna-ai vanna up to 2.0.2. Affected is the function exec of the file /src/vanna/legacy. Such manipulation leads to injection. The attack can be executed remotely. The exploit has been disclosed publicly and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component), CWE-707 (Improper Neutralization)

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


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

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

## Is CVE-2026-4511 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-4511 is a medium-severity code injection vulnerability in vanna-ai vanna, published on 21 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-4511 exists.

Affected product: vanna-ai vanna. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-4511/ (Markdown: https://insights.sbomify.com/CVE-2026-4511/index.md)
```

## Sources

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

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