# CVE-2024-8055: Local File Read (LFI) by Prompt Injection via SnowFlake SQL in vanna-ai/vanna

> Attackers can read arbitrary local files on the server via SQL injection in Snowflake operations, exposing sensitive data.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Mar 2025
- **Updated:** 15 Oct 2025
- **Also known as:** GHSA-63gf-x2fr-8r32

## What is CVE-2024-8055?

CVE-2024-8055 is a high-severity SQL injection vulnerability in vanna-ai/vanna, published on 20 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vanna v0.6.3 is vulnerable to SQL injection via Snowflake database in its file staging operations using the `PUT` and `COPY` commands. This vulnerability allows unauthenticated remote users to read arbitrary local files on the victim server, such as `/etc/passwd`, by exploiting the exposed SQL queries through a Python Flask API.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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


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

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

## Is CVE-2024-8055 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-8055 is a high-severity SQL injection vulnerability in vanna-ai/vanna, published on 20 Mar 2025. 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-8055 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-2024-8055/ (Markdown: https://insights.sbomify.com/CVE-2024-8055/index.md)
```

## Sources

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

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