# CVE-2026-77294: TREK: Server-Side Request Forgery via User-Configurable LLM Base URL

> Authenticated users can exploit SSRF in TREK to access internal services and cloud metadata, potentially leading to credential disclosure and resource modification.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **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:** 24 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-fmq9-ggh3-647p

## What is CVE-2026-77294?

CVE-2026-77294 is a high-severity server-side request forgery vulnerability in mauriceboe TREK, published on 24 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

TREK is a collaborative travel planner. Prior to 3.3.0, TREK allows an authenticated user to store an attacker-controlled llm_base_url through the settings API when the LLM_PARSING feature is enabled. Write permission to the target trip instance is required to trigger the vulnerable AI-assisted import path. The value is consumed by the clients in server/src/nest/llm-parse/clients/openai-compatible.client.ts, server/src/nest/llm-parse/clients/anthropic.client.ts, and server/src/nest/llm-parse/router/ollama-format.client.ts without applying the server-side request forgery guard. Triggering AI-assisted trip parsing causes the server to request the supplied destination, and upstream error response text can be returned in parsing warnings. This permits internal service discovery and access to link-local cloud metadata, with possible disclosure of infrastructure credentials and subsequent modification of protected cloud resources. This issue is fixed in version 3.3.0.

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

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


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

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

## Is CVE-2026-77294 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-77294 is a high-severity server-side request forgery vulnerability in mauriceboe TREK, published on 24 Sep 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-77294 exists.

Affected product: mauriceboe TREK. 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-77294/ (Markdown: https://insights.sbomify.com/CVE-2026-77294/index.md)
```

## Sources

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

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