# CVE-2026-114075: Trigger.dev authorization bypass in alert channels API

Source: https://junglewise.ai/threats/cve-2026-114075-trigger-dev-before-4-5-12-contains-an-authorization-bypass  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-21. Updated: 2026-10-21  
License: CC BY 4.0 with a link back

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](https://junglewise.ai/threats/technologies/trigger-dev). Vendors: [Trigger.dev](https://junglewise.ai/threats/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

- [https://github.com/triggerdotdev/trigger.dev/security/advisories/GHSA-wpjq-q67r-pg6m](https://github.com/triggerdotdev/trigger.dev/security/advisories/GHSA-wpjq-q67r-pg6m)
- [https://www.vulncheck.com/advisories/trigger-dev-before-4.5.12-authorization-bypass-via-alert-channels-api](https://www.vulncheck.com/advisories/trigger-dev-before-4.5.12-authorization-bypass-via-alert-channels-api)

## Related threats

- [Trigger.dev cross-site request forgery in logout endpoint](https://junglewise.ai/threats/cve-2026-114093-trigger-dev-before-4-5-6-contains-a-cross-site-request-forgery)
- [Trigger.dev missing authentication in task run replay](https://junglewise.ai/threats/cve-2026-114092-trigger-dev-before-4-5-0-performs-no-authentication-or)
- [Trigger.dev cross-tenant authorization bypass in run replay](https://junglewise.ai/threats/cve-2026-114091-trigger-dev-before-4-5-0-looks-up-runs-by-friendlyid-alone-in)
- [Trigger.dev cross-site request forgery in CLI authorization flow](https://junglewise.ai/threats/cve-2026-114089-trigger-dev-before-4-5-2-contains-a-cross-site-request-forgery)
- [Trigger.dev hardcoded default secret authentication bypass in Socket.IO](https://junglewise.ai/threats/cve-2026-114088-trigger-dev-before-4-5-4-contains-a-hardcoded-default-secret)