CVE-2026-114080
Deferred Deferred - Pending Action

Blind SSRF in Trigger.dev via Unvalidated Webhook URLs

Publication date: 2026-10-21

Last updated on: 2026-10-21

Assigner: VulnCheck

Description
Trigger.dev before 4.5.2 contains a blind server-side request forgery vulnerability that allows authenticated project members to make the server send requests by setting unvalidated alert-channel webhook URLs. Attackers can create alert channels pointing to loopback, internal, or cloud metadata addresses, then trigger alerts to probe internal service reachability and send signed POST requests.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-21
Last Modified
2026-10-21
Generated
2026-11-10
AI Q&A
2026-10-21
EPSS Evaluated
2026-11-08
NVD
CVE-2026-114080
EUVD
EUVD-2026-106883

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
triggerdotdev trigger.dev 0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-918 The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-114080 is a blind Server-Side Request Forgery (SSRF) vulnerability in Trigger.dev versions before 4.5.2. Authenticated project members can set unvalidated alert-channel webhook URLs, causing the server to send requests to attacker-controlled destinations like loopback, internal, or cloud metadata addresses. The server makes POST requests to these URLs without proper SSRF protections.

Detection Guidance

Check for unauthorized alert channels configured with suspicious URLs pointing to loopback, internal, or cloud metadata addresses. Review server logs for POST requests to unexpected destinations. Inspect network traffic for outbound connections from the trigger.dev server to internal or external services.

Impact Analysis

This vulnerability allows attackers to probe internal network services, check reachability of cloud metadata endpoints, and send signed POST requests to attacker-controlled servers. It requires low privileges and no user interaction, making it exploitable by any authenticated project member.

Compliance Impact

This vulnerability could potentially impact compliance with GDPR and HIPAA by enabling unauthorized internal network probing and data exfiltration. Attackers could use the SSRF flaw to access internal services or cloud metadata, which may include sensitive data or system configurations. This could lead to violations of data protection requirements under GDPR (e.g., unauthorized access to personal data) and HIPAA (e.g., breaches of protected health information).

Mitigation Strategies

Upgrade trigger.dev to version 4.5.2 or later. Implement server-side outbound URL validation to block loopback, private, and metadata addresses. Review existing alert channels for unauthorized configurations and remove any suspicious entries.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-114080. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...