{"id":"CVE-2026-114070","kind":"vulnerability","aliases":["CVE-2026-114070"],"related":[],"title":"Trigger.dev: dashboard agent proxy leaks user actor token to session readers","description":"Trigger.dev 4.5.0 before 4.6.0 contains an information disclosure vulnerability in the Dashboard Agent input proxy that stores a delegated user-actor token in browser-readable session input records. Attackers holding a chat's public session token can read the in records endpoint to recover the token from payload.metadata.userActorToken and replay it for environment JWT exchange.","summary":"Trigger.dev versions 4.5.0 before 4.6.0 store a delegated user-actor token in browser-readable session input records in the Dashboard Agent input proxy. An attacker holding a chat's public session token can read that token from the input records endpoint and replay it for an environment JWT exchange.","severity":"medium","cvss":5.1,"epss":0.00244,"exploited":false,"exploited_at":null,"products":[],"ecosystems":[],"tags":["dashboard-agent","package","self-hosted","trigger.dev"],"not_affected_if":["default-config"],"how_to_check":"- Check the installed Trigger.dev version in the project or deployment (for example `npx trigger.dev@latest --version` or the package.json entry); versions `4.5.0` through `4.5.x` are in the affected range.\n- Look for the Dashboard Agent chat feature being enabled and whether public session tokens are shared outside the team.","fix":"- Upgrade Trigger.dev to `4.6.0` or later.\n- Rotate any user-actor tokens or environment JWTs that may have been exposed through chat session input records.","status":"open","published_at":"2026-10-21T01:17:30+00:00","first_seen_at":"2026-10-23T21:57:27+00:00","triaged_at":"2026-10-25T04:29:00+00:00","updated_at":"2026-10-25T04:29:00+00:00","category":"package","confidence":0.6,"triage":{"at":"2026-10-25T04:29:00Z","model":"claude-haiku-5-5","output":{"fix":"- Upgrade Trigger.dev to `4.6.0` or later.\n- Rotate any user-actor tokens or environment JWTs that may have been exposed through chat session input records.","reach":"internet","title":"Trigger.dev: dashboard agent proxy leaks user actor token to session readers","impact":"medium","summary":"Trigger.dev versions 4.5.0 before 4.6.0 store a delegated user-actor token in browser-readable session input records in the Dashboard Agent input proxy. An attacker holding a chat's public session token can read that token from the input records endpoint and replay it for an environment JWT exchange.","category":"package","nicknames":[],"who_cares":["trigger.dev","self-hosted","dashboard-agent"],"confidence":0.6,"needs_auth":"unknown","worst_case":"Attacker replays a recovered user-actor token to obtain environment JWTs.","analyst_note":"Check the NVD entry and Trigger.dev release notes for the 4.6.0 fix and for whether Dashboard Agent is enabled by default; sources did not give a how-to-check or fix detail beyond the version range.","how_to_check":"- Check the installed Trigger.dev version in the project or deployment (for example `npx trigger.dev@latest --version` or the package.json entry); versions `4.5.0` through `4.5.x` are in the affected range.\n- Look for the Dashboard Agent chat feature being enabled and whether public session tokens are shared outside the team.","needs_analyst":true,"not_affected_if":["default-config"],"who_is_affected":"Teams that run self-hosted or cloud Trigger.dev 4.5.0 through versions before 4.6.0 with the Dashboard Agent feature in use. Exposure depends on a public chat session token being obtained, so deployments that do not use the Dashboard Agent or do not expose session tokens are less at risk.","user_interaction":"no","needs_special_setup":"unknown","severity_if_unknown":"medium"},"cost_usd":0.000681,"input_tokens":3395,"output_tokens":683,"severity_before":"medium"},"analyst_status":null,"analyst_note":null,"search":"'-114070':14A,17A '-2026':13A,16A '4.5.0':28B,78C '4.6.0':30B,80C 'actor':7A,36B,98C 'agent':3A,20B,48B,89C 'attack':52B,107C 'browser':40B,102C 'browser-read':39B,101C 'chat':55B,110C 'contain':81C 'cve':12A,15A 'dashboard':2A,19B,47B,88C 'dashboard-ag':18B 'deleg':33B,95C 'disclosur':84C 'endpoint':68B,120C 'environ':74B,131C 'exchang':76B,133C 'hold':53B,108C 'host':24B 'inform':83C 'input':43B,49B,66B,90C,105C 'jwt':75B,132C 'leak':5A 'packag':21B 'payload.metadata.useractortoken':126C 'proxi':4A,50B,91C 'public':57B,112C 'read':61B,116C 'readabl':41B,103C 'reader':11A 'record':44B,67B,106C,119C 'recov':122C 'replay':70B,128C 'self':23B 'self-host':22B 'session':10A,42B,58B,104C,113C 'store':31B,93C 'token':8A,37B,59B,63B,99C,114C,124C 'trigger.dev':1A,25B,26B,77C 'user':6A,35B,97C 'user-actor':34B,96C 'version':27B 'vulner':85C","nicknames":[],"mitigations":[],"who_affected":"Teams that run self-hosted or cloud Trigger.dev 4.5.0 through versions before 4.6.0 with the Dashboard Agent feature in use. Exposure depends on a public chat session token being obtained, so deployments that do not use the Dashboard Agent or do not expose session tokens are less at risk.","tier":"C","verified":{},"analyst_revisit_at":null,"first_public_at":"2026-10-21T01:17:30+00:00","kev":null,"cvss_vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:N/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-114070","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-114070","severity":null,"published_at":"2026-10-21T01:17:30+00:00","modified_at":"2026-10-21T16:17:30+00:00","first_seen_at":"2026-10-23T21:57:27+00:00","fetched_at":"2026-10-23T22:29:01+00:00","note":null},{"source":"epss","external_id":"CVE-2026-114070","url":"https://api.first.org/data/v1/epss?cve=CVE-2026-114070","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"}