{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-77294 exists.","fix":"No fix has been published for CVE-2026-77294 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-77294 and fix it if it is affected.\n\nWhat 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.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-77294 exists.\n\nAffected product: mauriceboe TREK. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-77294/ (Markdown: https://insights.sbomify.com/CVE-2026-77294/index.md)","id":"CVE-2026-77294","markdown":"https://insights.sbomify.com/CVE-2026-77294/index.md","name":"CVE-2026-77294","record":{"aliases":["GHSA-fmq9-ggh3-647p"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","privilege_escalation"],"network_reachable":"yes","non_default_config":true,"product_category":"TREK travel planner","requires_auth":"low_privilege","summary":"Authenticated users can exploit SSRF in TREK to access internal services and cloud metadata, potentially leading to credential disclosure and resource modification.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"TREK: Server-Side Request Forgery via User-Configurable LLM Base URL","id":"CVE-2026-77294","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"SeaweedFS S3 OIDC Bearer authentication bypasses IAM role trust policy","id":"CVE-2026-77298"},"packages":[],"prev":{"headline":"TREK: Cross-user note-file deletion (IDOR / Broken Access Control)","id":"CVE-2026-77293"},"products":["TREK"],"published":"2026-09-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-09-24","vendors":["mauriceboe"]},"summary":"Authenticated users can exploit SSRF in TREK to access internal services and cloud metadata, potentially leading to credential disclosure and resource modification.","url":"https://insights.sbomify.com/CVE-2026-77294/"}