# CVE-2024-8099: Server-Side Request Forgery (SSRF) in vanna-ai/vanna

> Attackers can exploit DuckDB features in vanna-ai/vanna to perform Server-Side Request Forgery, accessing internal resources and sensitive data.

- **Severity:** High 8.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L`)
- **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:** 20 Mar 2025
- **Also known as:** GHSA-cppx-6f25-3qxc

## What is CVE-2024-8099?

CVE-2024-8099 is a high-severity server-side request forgery 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

A Server-Side Request Forgery (SSRF) vulnerability exists in the latest version of vanna-ai/vanna when using DuckDB as the database. An attacker can exploit this vulnerability by submitting crafted SQL queries that leverage DuckDB's default features, such as `read_csv`, `read_csv_auto`, `read_text`, and `read_blob`, to make unauthorized requests to internal or external resources. This can lead to unauthorized access to sensitive data, internal systems, and potentially further attacks.

Weakness: CWE-918 (Server-Side Request Forgery)

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


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

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

## Is CVE-2024-8099 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-8099 is a high-severity server-side request forgery 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-8099 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-8099/ (Markdown: https://insights.sbomify.com/CVE-2024-8099/index.md)
```

## Sources

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

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