Live › vulnerability › CVE-2026-114070
Go to dashboardTrigger.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.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
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.
No product ranges from the sources yet.
npx trigger.dev@latest --version or the package.json entry); versions 4.5.0 through 4.5.x are in the affected range.4.6.0 or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-114070")
NVD data is provided by NIST and is public domain · EPSS scores by FIRST, used with attribution. Posts quoted belong to their authors.