CVE-2026-77294: CWE-918: Server-Side Request Forgery (SSRF) in mauriceboe TREK
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.
AI Analysis
Technical Summary
TREK versions before 3.3.0 contain an SSRF vulnerability (CWE-918) where an authenticated user with write access to a trip instance can control the llm_base_url setting if the LLM_PARSING feature is enabled. This setting is consumed by server-side clients (openai-compatible.client.ts, anthropic.client.ts, ollama-format.client.ts) without applying SSRF guards. Triggering AI-assisted trip parsing causes the server to make HTTP requests to the attacker-controlled URL, which can return upstream error responses visible in parsing warnings. This allows attackers to perform internal service discovery and access link-local cloud metadata endpoints, risking exposure of infrastructure credentials and unauthorized modification of cloud resources. The vulnerability is resolved in TREK version 3.3.0.
Potential Impact
An attacker with authenticated write access to a trip instance can exploit this SSRF vulnerability to make the server perform arbitrary HTTP requests. This can lead to internal network reconnaissance and access to sensitive cloud metadata services, potentially disclosing infrastructure credentials. Such credentials could be used to modify protected cloud resources, posing a significant security risk. The CVSS score of 8.1 reflects high impact on confidentiality and integrity, with no impact on availability.
Mitigation Recommendations
Upgrade TREK to version 3.3.0 or later, where this SSRF vulnerability is fixed. Until the upgrade, restrict write permissions on trip instances to trusted users and consider disabling the LLM_PARSING feature if not required. No other mitigations are specified by the vendor advisory.
CVE-2026-77294: CWE-918: Server-Side Request Forgery (SSRF) in mauriceboe TREK
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.
CVSS v3.1
Score 8.1high
Affected software
mauriceboe
TREK
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
TREK versions before 3.3.0 contain an SSRF vulnerability (CWE-918) where an authenticated user with write access to a trip instance can control the llm_base_url setting if the LLM_PARSING feature is enabled. This setting is consumed by server-side clients (openai-compatible.client.ts, anthropic.client.ts, ollama-format.client.ts) without applying SSRF guards. Triggering AI-assisted trip parsing causes the server to make HTTP requests to the attacker-controlled URL, which can return upstream error responses visible in parsing warnings. This allows attackers to perform internal service discovery and access link-local cloud metadata endpoints, risking exposure of infrastructure credentials and unauthorized modification of cloud resources. The vulnerability is resolved in TREK version 3.3.0.
Potential Impact
An attacker with authenticated write access to a trip instance can exploit this SSRF vulnerability to make the server perform arbitrary HTTP requests. This can lead to internal network reconnaissance and access to sensitive cloud metadata services, potentially disclosing infrastructure credentials. Such credentials could be used to modify protected cloud resources, posing a significant security risk. The CVSS score of 8.1 reflects high impact on confidentiality and integrity, with no impact on availability.
Mitigation Recommendations
Upgrade TREK to version 3.3.0 or later, where this SSRF vulnerability is fixed. Until the upgrade, restrict write permissions on trip instances to trusted users and consider disabling the LLM_PARSING feature if not required. No other mitigations are specified by the vendor advisory.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-08-20T19:17:14.374Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6ab56ceaf7a7c54106ad2a26
Added to database: 09/24/2026, 18:33:14 UTC
Last enriched: 09/24/2026, 18:47:56 UTC
Last updated: 09/25/2026, 02:20:02 UTC
Views: 10
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.