{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-54508 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-54508 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-54508 is a medium-severity server-side request forgery vulnerability in mauriceboe TREK, published on 20 Aug 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-54508 and fix it if it is affected.\n\nWhat it is: CVE-2026-54508 is a medium-severity server-side request forgery vulnerability in mauriceboe TREK, published on 20 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-54508 in the wild and no public exploit code.\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-54508/ (Markdown: https://insights.sbomify.com/CVE-2026-54508/index.md)","id":"CVE-2026-54508","markdown":"https://insights.sbomify.com/CVE-2026-54508/index.md","name":"CVE-2026-54508","record":{"aliases":["GHSA-f5vh-p2h5-x735"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"TREK travel planner","requires_auth":"low_privilege","summary":"Authenticated users can trigger blind SSRF attacks against internal services via unvalidated redirects in URL import and resolution features.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"TREK is a collaborative travel planner. Prior to 3.1.0, TREK validates only the initial URL before native redirect following in importGoogleList() and importNaverList() in server/src/services/placeService.ts and resolveGoogleMapsUrl() in server/src/services/mapsService.ts. The affected sinks call checkSsrf() from server/src/utils/ssrfGuard.ts and then use fetch() with redirect: 'follow' instead of the DNS-pinned safeFetch() path, so a public attacker-controlled URL can redirect the server to loopback, RFC 1918, or cloud metadata addresses without revalidation. An authenticated trip member can reach the list-import routes, and any authenticated user can reach /api/maps/resolve-url, allowing blind GET requests to internal services without response-body reflection. This issue is fixed in version 3.1.0.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"TREK: Blind SSRF via unvalidated redirect-following in Google/Naver list import and Maps URL resolution","id":"CVE-2026-54508","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"TREK IDOR: any authenticated user can read another user's journey share token (full journey leak)","id":"CVE-2026-54509"},"packages":[],"prev":{"headline":"Vvveb oEmbedProxy vulnerable to server-side request forgery","id":"CVE-2026-54507"},"products":["TREK"],"published":"2026-08-20","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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-21","vendors":["mauriceboe"]},"summary":"Authenticated users can trigger blind SSRF attacks against internal services via unvalidated redirects in URL import and resolution features.","url":"https://insights.sbomify.com/CVE-2026-54508/"}