CVE-2026-114070
Deferred Deferred - Pending Action

Information Disclosure in Trigger.dev Dashboard Agent

Publication date: 2026-10-21

Last updated on: 2026-10-21

Assigner: VulnCheck

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-21
Last Modified
2026-10-21
Generated
2026-11-10
AI Q&A
2026-10-21
EPSS Evaluated
2026-11-08
NVD
CVE-2026-114070
EUVD
EUVD-2026-107021

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
triggerdotdev trigger.dev 4.5.0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-522 The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

Trigger.dev versions 4.5.0 through 4.5.9 have an information disclosure vulnerability in the Dashboard Agent input proxy. The flaw allows attackers with a chat's public session token to retrieve a delegated user-actor token from browser-readable session input records via the records endpoint. This token can then be replayed to perform an environment JWT exchange.

Detection Guidance

Check Trigger.dev Dashboard Agent session input records for exposed user-actor tokens in payload.metadata.userActorToken via the records endpoint. Use network monitoring tools to inspect chat session tokens and validate if they grant access to session records containing delegated tokens.

Impact Analysis

An attacker with a public session token could extract the user-actor token from session records and use it to gain unauthorized access to the environment by exchanging it for a JWT. This could lead to unauthorized actions or data access within the affected system.

Compliance Impact

This vulnerability could potentially violate compliance with GDPR and HIPAA due to unauthorized access to user tokens. Exposure of delegated user-actor tokens may lead to unauthorized data access or processing, which conflicts with GDPR's data protection principles and HIPAA's safeguards for protected health information.

Mitigation Strategies

Upgrade Trigger.dev to version 4.6.0 or later immediately to address the vulnerability. If upgrading is not possible, restrict access to the records endpoint and invalidate all active session tokens to prevent token replay attacks.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-114070. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...