CVE-2026-114076: Trigger.dev before 4.5.2 Blind SSRF via Alert Channel Webhook URL
Noroxi assessment
Priority: Monitor (action score 21/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.33% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: triggerdotdev trigger.dev 4.5.2.
Low priority for now. Upgrade to triggerdotdev trigger.dev 4.5.2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Trigger.dev before 4.5.2 contains a blind server-side request forgery vulnerability that allows authenticated tenants to make the webapp server send POST requests to internal hosts by setting an unvalidated webhook alert channel URL. Attackers can point the webhook at internal services or cloud metadata addresses and trigger alerts to scan internal hosts, send state-changing POSTs, or reach IMDSv1 via redirects.
- Published
- Oct 21, 2026
- Updated
- Oct 28, 2026
- EPSS
- 0.3% · 26th percentile
- CWE
- CWE-918
Report tools
Action score
21
Low priority for now.
- CVSS
- 21 / 40 · 5.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · VulnCheck
- 5.3
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (VulnCheck). Independent of NVD's CPE analysis and usually ahead of it.
triggerdotdev trigger.dev
- 4.5.2not affected
- before 4.5.2affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| npm | trigger.dev | before 4.5.2 | 4.5.2 |
Same product
triggerdotdev: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-73656Trigger.dev: Cross-project deployment worker registration can modify another project's deployment state39Monitor
- CVE-2026-114087Trigger.dev before 4.5.6 Authentication Bypass via Hardcoded Default Secrets36Monitor
- CVE-2026-114085Trigger.dev through 4.7.6 Missing Authentication in Supervisor Workload API35Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-114074Oct 21, 2026 · Trigger.dev before 4.5.10 Webhook SSRF Protection Bypass via 198.18.0.0/15 Range21Monitor
- ← EarlierCVE-2026-114075Oct 21, 2026 · Trigger.dev before 4.5.12 Authorization Bypass via Alert Channels API21Monitor
- Later →CVE-2026-114077Oct 21, 2026 · Trigger.dev before 4.5.6 Cross-Tenant Deployment Hijack via createDeploymentBackgroundWorkerV424Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| triggerdotdev trigger.dev | 4.5.2 | Vendor (CNA) |
| npm:trigger.dev | 4.5.2 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recorded+1 d
- TodayNov 13, 2026+24 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- CyberKareemfinder
- dizconnectzreporter
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-1140740 days apartTrigger.dev before 4.5.10 Webhook SSRF Protection Bypass via 198.18.0.0/15 Range21Monitor
- CVE-2026-1140800 days apartTrigger.dev before 4.5.2 Blind SSRF via Alert-Channel Webhook URL21Monitor
- CVE-2026-8565047 days apartTrigger.dev before 4.5.2 Server-Side Request Forgery via webhook alert-channel21Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
- CVE-2026-1140870 days apartTrigger.dev before 4.5.6 Authentication Bypass via Hardcoded Default Secrets36Monitor
- CVE-2026-1140850 days apartTrigger.dev through 4.7.6 Missing Authentication in Supervisor Workload API35Monitor
- CVE-2026-1140920 days apartTrigger.dev before 4.5.0 Missing Authentication in Dashboard Run Replay Action33Monitor
Not on record for this CVE: patch commit or PR link · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-918 · Server-Side Request Forgery (SSRF)CVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- SSVC exploitation— → poc
- Fix✗ → ✓
- Exploit maturity— → none
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.