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-114067 Overview
CVE-2026-114067 is an improper authorization vulnerability [CWE-863] in Trigger.dev versions 4.5.0 before 4.6.2. The flaw resides in the PUT snapshot-url session endpoint, which fails to enforce a secret-key-only check. Holders of a public session token can request presigned Amazon S3 write URLs through the route. Attackers abuse these URLs to overwrite the durable chat snapshot tied to their own session. The result is a forged agent conversation history that misrepresents prior interactions with the Trigger.dev agent.
Critical Impact
End users with only a public session token can forge agent conversation history by overwriting durable chat snapshots in S3, undermining the integrity of agent interactions and downstream automation.
Affected Products
- Trigger.dev 4.5.0
- Trigger.dev versions after 4.5.0 and before 4.6.2
- Deployments exposing the PUT snapshot-url session route
Discovery Timeline
- 2026-10-21 - CVE-2026-114067 published to the National Vulnerability Database (NVD)
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2026-114067
Vulnerability Analysis
Trigger.dev issues two credential classes: a server-side secret key and a client-facing public session token. The PUT snapshot-url session endpoint is intended for privileged, server-side use because it mints presigned S3 URLs that can write durable chat snapshots. In vulnerable builds, the route authorizes any caller presenting a valid public session token. This permits browser-side clients and token-scraping attackers to request S3 write URLs for their own session scope. Once a presigned URL is returned, the attacker uploads an arbitrary JSON payload that becomes the canonical conversation history for that session.
Root Cause
The authorization check on the PUT snapshot-url handler does not distinguish between the public session token and the secret key. The route should restrict presigned S3 write issuance to the secret-key authentication path. The missing check maps directly to [CWE-863] Incorrect Authorization.
Attack Vector
Exploitation requires network access to the Trigger.dev API and a valid public session token, which end users already hold. The attacker sends a PUT request to the snapshot URL session endpoint, receives a presigned S3 URL scoped to the agent's durable snapshot object, and performs an HTTP PUT to that URL with a tampered JSON transcript. Subsequent agent reads trust the fabricated history. This enables repudiation, prompt-history manipulation, and downstream logic abuse where agents react to injected prior turns.
The vulnerability affects integrity only. See the GitHub Security Advisory GHSA-pc95-gc74-wg87 and the VulnCheck Advisory for Trigger.dev 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 AttacksDetection Methods for CVE-2026-114067
Indicators of Compromise
- Requests to the PUT /snapshot-url session endpoint authenticated with a public session token rather than the secret key.
- S3 access logs showing PutObject operations against durable chat snapshot keys that originate from end-user IP ranges.
- Unexpected modifications to snapshot objects outside normal agent write patterns, such as writes without a preceding agent run event.
Detection Strategies
- Correlate Trigger.dev API logs with S3 bucket audit logs to flag presigned URL issuance tied to public tokens.
- Alert on snapshot object versions whose content hash changes without a corresponding server-side agent completion event.
- Baseline the normal caller identity for snapshot writes and alert on deviations.
Monitoring Recommendations
- Enable S3 server access logging and AWS CloudTrail data events on buckets backing Trigger.dev durable snapshots.
- Monitor rates of presigned URL requests per session token and alert on anomalous spikes.
- Review Trigger.dev application logs for snapshot-url route authorizations granted to non-secret-key callers.
How to Mitigate CVE-2026-114067
Immediate Actions Required
- Upgrade Trigger.dev to version 4.6.2 or later across all self-hosted and managed deployments.
- Rotate any public session tokens that may have been exposed to untrusted clients during the vulnerable window.
- Audit S3 snapshot buckets for recent unexpected object versions and restore known-good snapshots from version history where tampering is suspected.
Patch Information
Trigger.dev addressed the issue in version 4.6.2 by restricting the PUT snapshot-url session endpoint to secret-key authentication. Operators should review the GitHub Security Advisory GHSA-pc95-gc74-wg87 for upgrade guidance and release notes.
Workarounds
- Block or proxy-filter requests to the PUT snapshot-url session route at the edge until the upgrade is deployed.
- Enable S3 object versioning on snapshot buckets so tampered objects can be rolled back.
- Treat agent conversation history read from durable snapshots as untrusted input and validate against server-side event logs before use in downstream automation.
# Upgrade Trigger.dev to the patched release
npm install trigger.dev@4.6.2
# Or with pnpm
pnpm add trigger.dev@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

