CVE-2026-125114: Api · Novu has SSRF via conditions filter webhook bypasses validateUrlSsrf() protection
Affects @novu/apiSource GCVE Database
Not known to be exploited · CVSS 8.3 High : upgrade to 3.15.0 soon.
Data as of 9 Nov 2026, 23:20 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 4.0 | 8.3 |
|---|
- Patch
- Available – fixed in 3.15.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 9 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.
What to do
Upgrade @novu/api to 3.15.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npm@novu/api | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available in @novu/api version 3.15.0 that adds SSRF validation using the validateUrlSsrf() function before sending POST requests in the conditions filter webhook. Users should upgrade to version 3.15.0 or later to remediate this vulnerability. The fix involves extracting validateUrlSsrf() to a shared utility and applying it to the webhook URL before the axios.post() call to block requests to private IP ranges.
Description
A Server-Side Request Forgery (SSRF) vulnerability exists in the conditions filter webhook of the @novu/api package prior to version 3.15.0. The webhook sends POST requests to user-configured URLs without applying SSRF validation, allowing attackers to make unauthorized internal network requests. This flaw bypasses the validateUrlSsrf() protection that is correctly applied elsewhere in the codebase. Exploitation can lead to reading sensitive internal data, such as AWS instance metadata credentials, which are returned and exposed via the execution details API.