# CVE-2026-108760: LlamaFarm through 0.0.34 Unauthenticated API Exposed on All Interfaces

> Network attackers can access the unauthenticated API to read keys, modify data, and delete projects due to insecure default binding.

- **Severity:** High 7.2 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-fhw6-pmfp-fhhf

## What is CVE-2026-108760?

CVE-2026-108760 is a high-severity vulnerability in llama-farm llamafarm, published on 11 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

LlamaFarm through 0.0.34 contains an insecure default configuration that binds its unauthenticated FastAPI server to 0.0.0.0 on port 14345, while the lf CLI silently discards HOST overrides. Network-adjacent attackers can call the project and dataset management API to read stored provider API keys, modify projects, trigger ingestion, and irreversibly delete projects.

Weakness: CWE-1327 (Binding to an Unrestricted IP Address)

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


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

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

## Is CVE-2026-108760 being exploited?

There is no known exploitation of CVE-2026-108760 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-108760 is a high-severity vulnerability in llama-farm llamafarm, published on 11 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-108760 in the wild and no public exploit code.

Affected product: llama-farm llamafarm. 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-108760/ (Markdown: https://insights.sbomify.com/CVE-2026-108760/index.md)
```

## Sources

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

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