Skip to main content
Vulnerability Database/CVE-2026-114082

CVE-2026-114082: Trigger.dev Authorization Bypass Vulnerability

CVE-2026-114082 is an authorization bypass flaw in Trigger.dev that lets attackers with public tokens access environment-wide credentials and manipulate session data. This post covers technical details, affected versions, impact, and mitigation.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-114082 Overview

CVE-2026-114082 is an authorization vulnerability in Trigger.dev versions prior to 4.6.2. The flaw allows public-token holders with session write access to obtain environment-wide S2 stream credentials through session input initialization. Attackers can use the leaked credential directly against the storage API to append, create, or trim session and run streams belonging to other users within the same environment. This enables forging stream output or permanently deleting records. The vulnerability is tracked under CWE-862: Missing Authorization.

Critical Impact

Public-token holders can forge output or permanently delete other users' session and run stream records across the entire environment.

Affected Products

  • Trigger.dev versions before 4.6.2

Discovery Timeline

  • 2026-10-21 - CVE-2026-114082 published to NVD
  • 2026-10-22 - Last updated in NVD database

Technical Details for CVE-2026-114082

Vulnerability Analysis

Trigger.dev is a background job and workflow orchestration platform. The vulnerability resides in the session input initialization path, which issues S2 stream credentials to clients holding public tokens with session write access. The issued credential is scoped to the entire environment rather than to the specific session or run that initiated the request. Public tokens are intended for narrow, delegated client-side use, so returning environment-wide credentials breaks the authorization boundary that separates tenant sessions and runs within a shared environment.

Root Cause

The underlying defect is a missing authorization check [CWE-862] during session stream credential issuance. The server does not verify that the requested credential scope matches the caller's permitted session or run. Instead, it returns a credential valid for every stream in the environment. Credential scoping is a design-level control, and its absence allows the storage API to treat the caller as a legitimate owner of unrelated streams.

Attack Vector

An attacker who holds a public token with session write access initiates a normal session input initialization request. The response contains an S2 stream credential that can be used directly against the storage API. The attacker then calls the storage API with the leaked credential to append arbitrary data to other users' streams, create new streams in their namespaces, or trim existing streams to delete records. No elevated privileges or user interaction are required beyond possession of a public token. See the GitHub Security Advisory GHSA-cpx8-cffg-mp4w and the VulnCheck advisory for additional technical context.

Detect Identity Attacks the Moment Authentication Fails

Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.

Stop Identity Attacks

Detection Methods for CVE-2026-114082

Indicators of Compromise

  • Unexpected append, create, or trim operations against S2 streams originating from public-token-derived credentials.
  • Session or run streams showing content that does not correlate with the owning user's recorded activity.
  • Missing or truncated run output records that previously existed in persisted storage.
  • Multiple distinct session or run stream IDs accessed by a single S2 credential within a short window.

Detection Strategies

  • Correlate S2 storage API access logs against the originating public token and verify the stream ID falls within that token's intended scope.
  • Baseline normal credential-to-stream cardinality and alert when a single credential writes to a statistically unusual number of streams.
  • Review Trigger.dev server logs for session input initialization calls that precede cross-session storage API writes.

Monitoring Recommendations

  • Centralize Trigger.dev application and S2 storage API logs in a SIEM for cross-source correlation.
  • Monitor stream deletion and trim operations as high-signal events requiring review.
  • Track issuance of S2 credentials and alert on credentials with environment-wide scope issued to public-token sessions.

How to Mitigate CVE-2026-114082

Immediate Actions Required

  • Upgrade Trigger.dev to version 4.6.2 or later across all self-hosted and managed deployments.
  • Rotate any public tokens that may have been exposed to untrusted clients prior to patching.
  • Audit S2 stream contents and run output history for signs of tampering or deletion since the vulnerable version was deployed.
  • Review existing public-token grants and revoke any that are not strictly required.

Patch Information

Trigger.dev version 4.6.2 corrects the authorization logic so that S2 stream credentials issued during session input initialization are scoped to the requesting session or run rather than the entire environment. Refer to the GitHub Security Advisory GHSA-cpx8-cffg-mp4w for release notes and remediation guidance.

Workarounds

  • If upgrading is not immediately possible, restrict issuance of public tokens with session write access to trusted internal services only.
  • Place the Trigger.dev API behind an authenticated proxy that enforces per-session scope checks on outbound S2 credentials.
  • Disable features that depend on client-side session input initialization until the patched version is deployed.
bash
# Upgrade Trigger.dev to the patched release
npm install @trigger.dev/sdk@^4.6.2

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.