# CVE-2024-5565: Prompt Injection in "ask" API with visualization leads to RCE

> Attackers can execute arbitrary Python code via prompt injection in the Vanna library's ask API when visualization is enabled.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 May 2024
- **Updated:** 25 Nov 2024
- **Also known as:** GHSA-7735-w2jp-gvg6, PYSEC-2026-561

## What is CVE-2024-5565?

CVE-2024-5565 is a high-severity code injection vulnerability in vanna, published on 31 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Vanna library uses a prompt function to present the user with visualized results, it is possible to alter the prompt using prompt injection and run arbitrary Python code instead of the intended visualization code. Specifically - allowing external input to the library’s “ask” method with "visualize" set to True (default behavior) leads to remote code execution.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2024-5565?

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


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

## How do I fix CVE-2024-5565?

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

## Is CVE-2024-5565 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-5565 and fix it if it is affected.

What it is: CVE-2024-5565 is a high-severity code injection vulnerability in vanna, published on 31 May 2024. 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-2024-5565 exists.

Affected packages and fixed versions:
- vanna (PyPI): affected all versions up to 0.5.5; no fix listed
- vanna (PyPI): affected all versions up to 0.5.5; no fix listed
- vanna (PyPI): affected all versions up to 0.5.5; 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-2024-5565/ (Markdown: https://insights.sbomify.com/CVE-2024-5565/index.md)
```

## Sources

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

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