Is CVE-2026-114067 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-114067 being exploited in the wild.

How severe is CVE-2026-114067?

Medium severity, with a CVSS score of 6.5, published 21 October 2026.

How is CVE-2026-114067 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-114067?

Check whether you run Trigger.dev at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-114067: Trigger.dev improper authorization in snapshot-url endpoint

CVE-2026-114067 · Severity: medium · CVSS 6.5 · Published 2026-10-21

Trigger.dev is a platform for building AI agent workflows with durable chat capabilities. A flaw in its snapshot-url API endpoint allows users to overwrite their own session's chat history, enabling them to forge conversations and mislead the AI agent about what was previously discussed. This affects versions 4.5.0 through 4.6.1.

Technologies: Trigger.dev. Vendors: Trigger.dev.

Quick answers

Is CVE-2026-114067 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-114067 being exploited in the wild.
How severe is CVE-2026-114067?: Medium severity, with a CVSS score of 6.5, published 21 October 2026.
Which products and versions are affected?: Trigger.dev 4.5.0 to 4.6.1.
Is there a fix for CVE-2026-114067?: Yes: fixed in 4.6.2. Until then: Restrict API access to trusted clients only or disable the snapshot-url endpoint until upgrading to the patched version. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-114067 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-114067?: Check whether you run Trigger.dev at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: 4.6.2

Restrict API access to trusted clients only or disable the snapshot-url endpoint until upgrading to the patched version.

Technical details

The PUT /api/v1/sessions/:sessionId/snapshot-url endpoint lacks a secret-key-only authentication check that exists in its sibling endpoint. This allows public session tokens (issued to browser clients) to obtain presigned S3 write URLs and overwrite the durable chat snapshot. The vulnerability stems from missing authorization.type !== "PRIVATE" validation, enabling session token holders to forge agent message history in the durable storage layer.

Affected products

Trigger.dev Trigger.dev 4.5.0 to 4.6.1

Timeline

2026-09-16: disclosed
2026-10-21: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.