{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-77320 exists.","fix":"No fix has been published for CVE-2026-77320 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-77320 is a medium-severity missing authorization vulnerability in mauriceboe TREK, published on 24 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-77320 and fix it if it is affected.\n\nWhat it is: CVE-2026-77320 is a medium-severity missing authorization vulnerability in mauriceboe TREK, published on 24 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-77320 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-77320/ (Markdown: https://insights.sbomify.com/CVE-2026-77320/index.md)","id":"CVE-2026-77320","markdown":"https://insights.sbomify.com/CVE-2026-77320/index.md","name":"CVE-2026-77320","record":{"aliases":["GHSA-9hc8-p7gm-p7mx"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"TREK travel planner","requires_auth":"none","summary":"Attackers with a valid share token can access hidden itinerary and location data in TREK because the server ignores the share_map permission setting.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-602","name":"Client-Side Enforcement of Server-Side Security"},{"id":"CWE-284","name":"Improper Access Control"},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"TREK is a collaborative travel planner. Prior to 3.3.0, getSharedTripData in server/src/services/shareService.ts returns days, assignments, dayNotes, and places through GET /api/shared/:token even when the trip owner disables share_map. The client hides the map, but the public JSON response still includes the itinerary and place names, coordinates, addresses, descriptions, notes, and prices. Anyone holding the valid share token can therefore read location and route information that the owner explicitly chose not to share, although the random token remains required and the flaw does not permit modification. 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":"Missing authorization in TREK","id":"CVE-2026-77320","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"TREK MCP trip summary bypasses delegated OAuth read scopes","id":"CVE-2026-77321"},"packages":[],"prev":{"headline":"SeaweedFS: SFTP path ACL literal prefix match permits cross-tenant file read and overwrite","id":"CVE-2026-77317"},"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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-29","vendors":["mauriceboe"]},"summary":"Attackers with a valid share token can access hidden itinerary and location data in TREK because the server ignores the share_map permission setting.","url":"https://insights.sbomify.com/CVE-2026-77320/"}