TREK: Server-Side Request Forgery via User-Configurable LLM Base URL (CVE-2026-77294) | HOL Guard CVE

High · CVSS 8.1CVE-2026-77294

TREK: Server-Side Request Forgery via User-Configurable LLM Base URL

Answer in brief

CVE-2026-77294 records a High severity (CVSS 8.1) vulnerability in TREK: Server-Side Request Forgery via User-Configurable LLM Base URL. The current sources do not mark it as known exploited. The current feed maps mauriceboe/TREK (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 24, 2026Updated Sep 24, 2026Source checked Sep 25, 2026First seen by HOL Sep 25, 2026Material review Sep 24, 2026

Upstream Advisory

Key facts

Risk: High · CVSS 8.1
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 8.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps mauriceboe/TREK (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
mauriceboe/TREKgeneric	<3.3.0	3.3.0

Recommended response

Check inventory. Check lockfiles and deployed manifests for mauriceboe/TREK.
Review the reported fix. Update mauriceboe/TREK to 3.3.0 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 24, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 24, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 25, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.