---
id: "CVE-2026-114082"
kind: "vulnerability"
aliases: ["CVE-2026-114082"]
title: "Trigger.dev: session input flaw leaks stream credentials, allowing forged or deleted streams"
severity: "high"
cvss: 8.1
epss: 0.00275
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["package", "self-hosted", "trigger.dev", "typescript"]
not_affected_if: ["version-4.6.2-or-later"]
published_at: "2026-10-21T01:17:32+00:00"
first_seen_at: "2026-10-23T21:57:27+00:00"
updated_at: "2026-10-25T03:05:57+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-114082", "first_seen_at": "2026-10-23T21:57:27+00:00"}, {"source": "epss", "url": "https://api.first.org/data/v1/epss?cve=CVE-2026-114082", "first_seen_at": "2026-10-24T13:15:55+00:00"}]
---

# Trigger.dev: session input flaw leaks stream credentials, allowing forged or deleted streams

Trigger.dev before 4.6.2 lets a holder of a public token with session write access obtain environment-wide S2 stream credentials through session input initialization. An attacker can use those credentials against the storage API to append, create, or trim other sessions' and runs' streams, forging output or permanently deleting records.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed Trigger.dev version (for example `npx trigger.dev@latest --version` or the version in `package.json`) and see whether it is below `4.6.2`
- unknown for other checks; the sources do not describe configuration details

## Fix

- Upgrade Trigger.dev to `4.6.2` or later
- unknown for credential rotation; the sources do not say whether S2 stream credentials issued before the upgrade should be rotated

## Timeline

- 2026-10-23T21:57:27+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-114082
- 2026-10-24T13:15:55+00:00 epss https://api.first.org/data/v1/epss?cve=CVE-2026-114082

## From the sources

Trigger.dev before 4.6.2 contains an authorization vulnerability that allows public-token holders with session write access to obtain environment-wide S2 stream credentials via session input initialization. Attackers can use the credential directly against the storage API to append, create, or trim other session and run streams, forging output or permanently deleting records.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_