CVE-2026-114080 triggerdotdev CVE debrief

Who should care

Defenders responsible for Trigger.dev installations, particularly those exposed to the internet or with sensitive internal services, should assess their exposure and take steps to mitigate the vulnerability.

Why it matters

CVE-2026-114080 is a blind SSRF vulnerability in Trigger.dev before 4.5.2, allowing authenticated project members to make server requests via unvalidated alert-channel webhook URLs. Defenders should prioritize verifying exposure, restricting access, and monitoring for suspicious activity.

• Probing of internal service reachability
• Sending signed POST requests to arbitrary addresses
• Potential for data exfiltration or unauthorized access

Technical summary

The vulnerability allows authenticated project members to set unvalidated alert-channel webhook URLs, enabling them to make the server send requests to arbitrary addresses. This could be used to probe internal service reachability and send signed POST requests. Attackers can create alert channels pointing to loopback, internal, or cloud metadata addresses, then trigger alerts. Defenders should prioritize verifying exposure of Trigger.dev installations to the internet and restricting access to authenticated project members.

Defensive priority

Defenders should prioritize verifying exposure of Trigger.dev installations to the internet and restricting access to authenticated project members. They should also monitor for suspicious alert-channel webhook activity and update to version 4.5.2 or later.

Recommended defensive actions

• Verify Trigger.dev installations are not exposed to the internet
• Restrict access to authenticated project members
• Monitor for suspicious alert-channel webhook activity
• Update to version 4.5.2 or later
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record and source item provide details on the vulnerability, including its description, affected versions, and references to vendor advisories. However, there is limited information on exploitation or victim impact.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.