# CVE-2026-114074: Trigger.dev webhook SSRF protection bypass via 198.18.0.0/15 range

Source: https://junglewise.ai/threats/cve-2026-114074-trigger-dev-before-4-5-10-contains-a-server-side-request-forgery  
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-114074 · Severity: medium · CVSS 5.4 · Published 2026-10-21

Trigger.dev is a workflow automation platform that uses webhooks to send alerts to external services. A security flaw allows authenticated users to bypass protections that prevent webhooks from targeting internal networks, enabling them to probe or interact with services inside a company's infrastructure that should be unreachable. The vulnerability affects versions before 4.5.10.

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-114074 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-114074 being exploited in the wild.

**How severe is CVE-2026-114074?** Medium severity, with a CVSS score of 5.4, published 21 October 2026.

**Which products and versions are affected?** Trigger.dev before 4.5.10.

**Is there a fix for CVE-2026-114074?** Yes: fixed in 4.5.10. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-114074 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-114074?** 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.10

## Technical details

The isUnsafeIPv4 function in Trigger.dev's webhook SSRF protection omits the RFC 6890 designated 198.18.0.0/15 benchmarking range when filtering dangerous destinations. An authenticated project member can configure alert-channel webhooks to POST to addresses in this range, which is treated as routable within deployments but globally non-standard. The vulnerability enables blind SSRF attacks—internal reachability probing, timing-based enumeration, and state-changing POST requests—but response bodies are not returned to the attacker.

## Affected products

- Trigger.dev Trigger.dev before 4.5.10

## Timeline

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

## References

- [https://github.com/triggerdotdev/trigger.dev/security/advisories/GHSA-fhh4-xvj5-m7pq](https://github.com/triggerdotdev/trigger.dev/security/advisories/GHSA-fhh4-xvj5-m7pq)
- [https://www.vulncheck.com/advisories/trigger-dev-before-4.5.10-webhook-ssrf-protection-bypass-via-198.18.0.0-15-range](https://www.vulncheck.com/advisories/trigger-dev-before-4.5.10-webhook-ssrf-protection-bypass-via-198.18.0.0-15-range)

## 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)