Live › vulnerability › CVE-2026-114067
Go to dashboardTrigger.dev versions 4.5.0 before 4.6.2 expose a PUT snapshot-url session endpoint that accepts public session tokens instead of requiring the secret key. A user holding a public session token can obtain presigned S3 write URLs and overwrite their own durable chat snapshot, forging the agent's conversation history.
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 running Trigger.dev 4.5.0 before 4.6.2 that use durable chat or agent sessions, where end users hold public session tokens and the agent's conversation snapshot is stored in S3. The exposure depends on the snapshot-url route being reachable with a public token; teams not using durable session snapshots are likely unaffected, but the sources do not state this explicitly.
No product ranges from the sources yet.
npx trigger.dev@latest --version or the @trigger.dev/sdk version in package.json; versions 4.5.0 through 4.5.x are affected.4.6.2 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.2 contains an improper authorization vulnerability in the PUT snapshot-url session endpoint that allows public session token holders to obtain presigned S3 write URLs. End users can overwrite their own session's durable chat snapshot to forge the agent's conversation history, since the route lacks a secret-key-only check.
This page as .md · .json · in your agent: get_signal("CVE-2026-114067")
NVD data is provided by NIST and is public domain · EPSS scores by FIRST, used with attribution. Posts quoted belong to their authors.