{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-114067 exists.","fix":"No fix has been published for CVE-2026-114067 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-114067 is a high-severity vulnerability in triggerdotdev trigger.dev, published on 21 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-114067 and fix it if it is affected.\n\nWhat it is: CVE-2026-114067 is a high-severity vulnerability in triggerdotdev trigger.dev, published on 21 Oct 2026. \nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-114067 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-114067/ (Markdown: https://insights.sbomify.com/CVE-2026-114067/index.md)","id":"CVE-2026-114067","markdown":"https://insights.sbomify.com/CVE-2026-114067/index.md","name":"CVE-2026-114067","record":{"aliases":["GHSA-4mgf-q8vv-4g8c","GHSA-pc95-gc74-wg87"],"analysis":null,"analysis_generated_by":null,"assigner":"VulnCheck","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"Trigger.dev 4.5.0 before 4.6.2 contains an improper authorization vulnerability in the PUT snapshot-url session endpoint that allows public session token holders to obtain presigned S3 write URLs. End users can overwrite their own session's durable chat snapshot to forge the agent's conversation history, since the route lacks a secret-key-only check.","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 4.5.0 before 4.6.2 Improper Authorization via snapshot-url Session Route","id":"CVE-2026-114067","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Trigger.dev before 4.6.0 Missing Authorization via Waitpoint Token Wait Endpoint","id":"CVE-2026-114068"},"packages":[],"prev":{"headline":"Trigger.dev before 4.7.0 Missing Authorization via Batch parentRunId Waitpoints","id":"CVE-2026-114066"},"products":["trigger.dev"],"published":"2026-10-21","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":"partial"},"state":"PUBLISHED","updated":"2026-10-22","vendors":["triggerdotdev"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-114067/"}