{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-73658 exists.","fix":"No fix has been published for CVE-2026-73658 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-73658 is a high-severity path traversal vulnerability in triggerdotdev trigger.dev, published on 13 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-73658 and fix it if it is affected.\n\nWhat it is: CVE-2026-73658 is a high-severity path traversal vulnerability in triggerdotdev trigger.dev, published on 13 Aug 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-73658 exists.\n\nAffected product: triggerdotdev trigger.dev. 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-73658/ (Markdown: https://insights.sbomify.com/CVE-2026-73658/index.md)","id":"CVE-2026-73658","markdown":"https://insights.sbomify.com/CVE-2026-73658/index.md","name":"CVE-2026-73658","record":{"aliases":["GHSA-888c-px7m-736v"],"analysis":{"component_type":"cloud_service","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"AI workflow platform","requires_auth":"low_privilege","summary":"Attackers with valid API keys can traverse paths to read or overwrite other tenants' task payloads in the object store.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"},{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"},{"id":"CWE-20","name":"Improper Input Validation"}],"description":"Trigger.dev is a platform for building and deploying fully managed AI agents and workflows. From 4.4.2 until 4.5.0-rc.5, Aws4FetchClient.buildUrl() and Aws4FetchClient.presign() in apps/webapp/app/v3/objectStoreClient.server.ts assign user-controlled packet keys to URL.pathname, while apps/webapp/app/routes/api.v1.packets.$.ts accepts params[\"*\"] without rejecting dot segments and uses findResource: async () =\u003e 1 without per-resource ownership validation. WHATWG path normalization collapses .. segments before signing, allowing a caller with a valid environment API key to obtain presigned URLs for another tenant's object-store keys and read or overwrite task payloads. This issue is fixed in version 4.5.0-rc.5.","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":"Trigger.dev: Cross-tenant object store read and write via URL path traversal","id":"CVE-2026-73658","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Trigger.dev: Cross-tenant object read/write via path traversal in packet presign API","id":"CVE-2026-73659"},"packages":[],"prev":{"headline":"Trigger.dev: Cross-tenant payload poisoning via packet write + replay","id":"CVE-2026-73657"},"products":["trigger.dev"],"published":"2026-08-13","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-08-14","vendors":["triggerdotdev"]},"summary":"Attackers with valid API keys can traverse paths to read or overwrite other tenants' task payloads in the object store.","url":"https://insights.sbomify.com/CVE-2026-73658/"}