Is CVE-2026-114092 exploited in the wild?

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

How severe is CVE-2026-114092?

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

Is there a fix for CVE-2026-114092?

Yes: fixed in 4.5.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-114092 attacked?

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

Am I affected by CVE-2026-114092?

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-114092: Trigger.dev missing authentication in task run replay

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

Trigger.dev is a task automation and scheduling platform. Before version 4.5.2, the task replay feature in both the dashboard and HTTP API lacked proper authentication and authorization checks, allowing attackers who know a victim's run ID to replay tasks in their own environments. This exposes task payloads containing secrets, database credentials, and API keys, and enables unauthorized task execution with the victim's permissions.

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

Quick answers

Is CVE-2026-114092 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-114092 being exploited in the wild.
How severe is CVE-2026-114092?: Medium severity, with a CVSS score of 6.5, published 21 October 2026.
Which products and versions are affected?: Trigger.dev before 4.5.2.
Is there a fix for CVE-2026-114092?: Yes: fixed in 4.5.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-114092 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-114092?: 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.5.2

Technical details

The vulnerability exists in two endpoints: the dashboard's POST /resources/taskruns/:runParam/replay lacks any authentication, while the API's POST /api/v1/runs/:runParam/replay authenticates by API key but fails to scope the query to the caller's environment. Both endpoints look up runs by globally-unique friendlyId without verifying the requesting user's organization membership. An authenticated attacker can replay any task run by providing a known friendlyId and a target environmentId they control, exposing the original task's payload and environment variables.

Affected products

Trigger.dev Trigger.dev before 4.5.2

Timeline

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

References

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