Is CVE-2026-114075 exploited in the wild?

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

How severe is CVE-2026-114075?

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

Is there a fix for CVE-2026-114075?

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

How is CVE-2026-114075 attacked?

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

Am I affected by CVE-2026-114075?

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-114075: Trigger.dev authorization bypass in alert channels API

CVE-2026-114075 · Severity: medium · CVSS 5.4 · Published 2026-10-21

Trigger.dev is a workflow automation platform that manages deployments and alerts for applications. An attacker with a read-only access token can bypass capability checks to create malicious webhook alert channels, routing deployment and error notifications to attacker-controlled servers. This allows attackers to intercept alerts and potentially extract sensitive alert metadata while compromising the integrity of alert routing.

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

Quick answers

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

Technical details

The legacy authenticateApiRequestWithPersonalAccessToken() helper accepts user-actor tokens (UATs) but drops their capability restrictions, returning only the userId. The POST /api/v1/projects/:projectRef/alertChannels endpoint uses this helper without performing capability checks, allowing a UAT restricted to read:runs to create production webhook alert channels with attacker-controlled URLs and parameters. The vulnerability is an authorization check bypass (CWE-863) exploitable over the network with low privilege requirements.

Affected products

Trigger.dev Trigger.dev before 4.5.12

Timeline

2026-08-20: disclosed
2026-10-21: advisory

References

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