{"answers":{"affected":"2 open source packages ship an affected version, including trigger.dev.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-85650 exists.","fix":"Upgrade trigger.dev to 4.5.2 or later.","what":"CVE-2026-85650 is a medium-severity server-side request forgery vulnerability in triggerdotdev trigger.dev, published on 4 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-85650 and fix it if it is affected.\n\nWhat it is: CVE-2026-85650 is a medium-severity server-side request forgery vulnerability in triggerdotdev trigger.dev, published on 4 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-85650 exists.\n\nAffected packages and fixed versions:\n- trigger.dev (npm): affected all versions; fixed in 4.5.2\n- trigger.dev (npm): affected all versions; fixed in 4.5.2\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-85650/ (Markdown: https://insights.sbomify.com/CVE-2026-85650/index.md)","id":"CVE-2026-85650","markdown":"https://insights.sbomify.com/CVE-2026-85650/index.md","name":"CVE-2026-85650","record":{"aliases":["GHSA-2463-rh88-r3gg","GHSA-xxv7-2vv3-h682","MINI-wcjg-7chg-mwm9"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Trigger.dev platform","requires_auth":"low_privilege","summary":"Authenticated users can exploit SSRF in webhook alert channels to access internal services and metadata endpoints via the server.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","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:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"Trigger.dev before 4.5.2 contains a server-side request forgery vulnerability in webhook alert channel delivery URLs that are fetched without validation or SSRF protection. Authenticated users with organization membership can create alert channels with URLs targeting internal services and metadata endpoints, allowing the server to issue POST requests to restricted resources.","ecosystems":["npm"],"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 before 4.5.2 Server-Side Request Forgery via webhook alert-channel","id":"CVE-2026-85650","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":2,"n_references":6,"next":{"headline":"Trigger.dev before 4.5.2 Unauthorized Environment Access via Run Replay","id":"CVE-2026-85651"},"packages":[{"ecosystem":"npm","fixed":["4.5.2"],"introduced":["0"],"last_affected":[],"package":"trigger.dev","purl":null,"source":"GHSA-xxv7-2vv3-h682"},{"ecosystem":"npm","fixed":["4.5.2"],"introduced":["0"],"last_affected":[],"package":"trigger.dev","purl":"pkg:npm/trigger.dev","source":"GHSA-xxv7-2vv3-h682"}],"prev":{"headline":"Auth bypass in software-actualizer","id":"CVE-2026-85649"},"products":["trigger.dev"],"published":"2026-09-04","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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-09-04","vendors":["triggerdotdev"]},"summary":"Authenticated users can exploit SSRF in webhook alert channels to access internal services and metadata endpoints via the server.","url":"https://insights.sbomify.com/CVE-2026-85650/"}