{"id":"CVE-2026-114088","kind":"vulnerability","aliases":["CVE-2026-114088"],"related":[],"title":"Trigger.dev: hardcoded coordinator secret lets outsiders read run environment variables","description":"Trigger.dev before 4.5.4 contains a hardcoded default secret vulnerability in the /coordinator Socket.IO namespace that allows unauthenticated attackers to connect using the published coordinator-secret value. Attackers can emit READY_FOR_EXECUTION to retrieve decrypted run environment variables or send TASK_RUN_FAILED_TO_RUN and similar events to tamper with arbitrary runs.","summary":"Trigger.dev before 4.5.4 ships a default coordinator secret in its /coordinator Socket.IO namespace that is published openly. An unauthenticated attacker who connects with it can request decrypted run environment variables or send forged run-status events to alter arbitrary runs.","severity":"high","cvss":8.3,"epss":0.00276,"exploited":false,"exploited_at":null,"products":[],"ecosystems":[],"tags":["node.js","package","self-hosted","socket.io","trigger.dev"],"not_affected_if":["managed-hosting","patched-version"],"how_to_check":"- Check the installed Trigger.dev version (e.g. `npx trigger.dev@latest --version` or the version pinned in `package.json`) and see whether it is below `4.5.4`.\n- Check whether the coordinator is reachable from outside your network and whether `COORDINATOR_SECRET` is set to a non-default value (the sources do not name the exact variable).","fix":"- Upgrade Trigger.dev to `4.5.4` or later.\n- Rotate any secrets and environment variables that were available to runs on an affected version, since they may have been read.","status":"open","published_at":"2026-10-21T01:17:33+00:00","first_seen_at":"2026-10-23T21:57:28+00:00","triaged_at":"2026-10-25T03:02:14+00:00","updated_at":"2026-10-25T03:02:14+00:00","category":"package","confidence":0.6,"triage":{"at":"2026-10-25T03:02:14Z","model":"claude-haiku-5-5","output":{"fix":"- Upgrade Trigger.dev to `4.5.4` or later.\n- Rotate any secrets and environment variables that were available to runs on an affected version, since they may have been read.","reach":"internet","title":"Trigger.dev: hardcoded coordinator secret lets outsiders read run environment variables","impact":"high","summary":"Trigger.dev before 4.5.4 ships a default coordinator secret in its /coordinator Socket.IO namespace that is published openly. An unauthenticated attacker who connects with it can request decrypted run environment variables or send forged run-status events to alter arbitrary runs.","category":"package","nicknames":[],"who_cares":["trigger.dev","self-hosted","node.js","socket.io"],"confidence":0.6,"needs_auth":"no","worst_case":"Attacker reads decrypted run environment variables and tampers with runs.","analyst_note":"Confirm from the NVD entry whether the default is set by the coordinator config and whether Trigger.dev Cloud is affected; check the Trigger.dev 4.5.4 release notes for the exact setting.","how_to_check":"- Check the installed Trigger.dev version (e.g. `npx trigger.dev@latest --version` or the version pinned in `package.json`) and see whether it is below `4.5.4`.\n- Check whether the coordinator is reachable from outside your network and whether `COORDINATOR_SECRET` is set to a non-default value (the sources do not name the exact variable).","needs_analyst":true,"not_affected_if":["patched-version","managed-hosting"],"who_is_affected":"Self-hosted Trigger.dev deployments running a version before `4.5.4` where the coordinator is reachable by untrusted clients are exposed. The sources do not say whether Trigger.dev Cloud is affected, so unknown. Teams that already run `4.5.4` or later can skip it.","user_interaction":"no","needs_special_setup":"unknown","severity_if_unknown":"high"},"cost_usd":0.000682,"input_tokens":3413,"output_tokens":681,"severity_before":"high"},"analyst_status":null,"analyst_note":null,"search":"'-114088':13A,16A '-2026':12A,15A '/coordinator':34B,76C '4.5.4':26B,67C 'allow':80C 'alter':62B 'arbitrari':63B,117C 'attack':43B,82C,92C 'connect':45B,84C 'contain':68C 'coordin':3A,30B,89C 'coordinator-secret':88C 'cve':11A,14A 'decrypt':50B,100C 'default':29B,71C 'emit':94C 'environ':9A,52B,102C 'event':60B,113C 'execut':97C 'fail':108C 'forg':56B 'hardcod':2A,70C 'host':21B 'let':5A 'namespac':36B,78C 'node.js':17B 'open':40B 'outsid':6A 'packag':18B 'publish':39B,87C 'read':7A 'readi':95C 'request':49B 'retriev':99C 'run':8A,51B,58B,64B,101C,107C,110C,118C 'run-status':57B 'secret':4A,31B,72C,90C 'self':20B 'self-host':19B 'send':55B,105C 'ship':27B 'similar':112C 'socket.io':22B,35B,77C 'status':59B 'tamper':115C 'task':106C 'trigger.dev':1A,23B,24B,65C 'unauthent':42B,81C 'use':85C 'valu':91C 'variabl':10A,53B,103C 'vulner':73C","nicknames":[],"mitigations":[],"who_affected":"Self-hosted Trigger.dev deployments running a version before `4.5.4` where the coordinator is reachable by untrusted clients are exposed. The sources do not say whether Trigger.dev Cloud is affected, so unknown. Teams that already run `4.5.4` or later can skip it.","tier":"B","verified":{},"analyst_revisit_at":null,"first_public_at":"2026-10-21T01:17:33+00:00","kev":null,"cvss_vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","cvss_by":"disclosure@vulncheck.com","poc_count":0,"sources":[{"source":"nvd","external_id":"CVE-2026-114088","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-114088","severity":null,"published_at":"2026-10-21T01:17:33+00:00","modified_at":"2026-10-21T01:17:33+00:00","first_seen_at":"2026-10-23T21:57:28+00:00","fetched_at":"2026-10-23T22:29:01+00:00","note":null},{"source":"epss","external_id":"CVE-2026-114088","url":"https://api.first.org/data/v1/epss?cve=CVE-2026-114088","severity":null,"published_at":null,"modified_at":null,"first_seen_at":"2026-10-24T13:15:55+00:00","fetched_at":"2026-10-24T13:15:55+00:00","note":null}],"documents":[],"notice":"Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai"}