Is CVE-2026-114091 exploited in the wild?

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

How severe is CVE-2026-114091?

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

Is there a fix for CVE-2026-114091?

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-114091 attacked?

It is attacked over the network, in a hosted service.

Am I affected by CVE-2026-114091?

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-114091: Trigger.dev cross-tenant authorization bypass in run replay

CVE-2026-114091 · Severity: medium · CVSS 5.3 · Published 2026-10-21

Trigger.dev is a workflow and task automation platform that runs background jobs for applications. An attacker with any tenant's API key can access and replay another organization's task runs if they know the run ID, allowing them to read sensitive task payload data from victims. This affects both the unauthenticated dashboard replay endpoint and the API replay endpoint, enabling cross-organization data theft.

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

Quick answers

Is CVE-2026-114091 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-114091 being exploited in the wild.
How severe is CVE-2026-114091?: Medium severity, with a CVSS score of 5.3, published 21 October 2026.
Which products and versions are affected?: Trigger.dev before 4.5.0.
Is there a fix for CVE-2026-114091?: 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-114091 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-114091?: 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 is a missing authorization check (CWE-862, CWE-306) in two replay endpoints: the dashboard route lacks authentication entirely, and the API route authenticates by API key but fails to scope the friendlyId lookup to the caller's runtime environment. Since friendlyId is globally unique and the ReplayTaskRunService does not verify that the supplied environmentId belongs to the same project as the original run, an attacker can clone any organization's task payload into an environment they control and read it.

Affected products

Trigger.dev Trigger.dev before 4.5.0

Timeline

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

References

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