Novu: SSRF via conditions filter webhook bypasses validateUrlSsrf() protection
Affects Novu versions before 3.15.0 whose workflows use a condition step with a webhook URL. No vendor rating is given; CVSS scores it 8.3 (high). Fixed in 3.15.0.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 3.15.0
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. A workflow condition step is configured with a webhook URL (the conditions filter webhook).
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 16/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Novu, a service for sending notifications through multiple channels, contains a server-side request forgery flaw in its workflow condition filter webhook. An attacker with low-privilege access can reach it over the network, making the server send a POST request to internal or link-local services and read back the response, which can expose credentials or internal data through the execution details API.
Read the original description
Novu provides an API for sending notifications through multiple channels. Prior to 3.15.0, the conditions filter webhook in libs/application-generic/src/usecases/conditions-filter/conditions-filter.usecase.ts passes the user-configured child.webhookUrl directly to axios.post without calling validateUrlSsrf. Evaluating a workflow condition can therefore make the worker send a POST request to a private or link-local service and return the response data for condition evaluation. The response is stored in execution details and exposed through GET /execution-details, which can disclose credentials from POST-capable metadata services or data from internal services, although metadata endpoints that require GET are not reachable through this path. This issue is fixed in version 3.15.0.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.3/10CVSS 8.3
- No patch0/5No signal
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 23 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
A workflow condition step is configured with a webhook URL (the conditions filter webhook).Upgrade to a fixed version: 3.15.0.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- novuhq novu
fixed in 3.15.0
Evidence 4
- Advisory
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-125114
Is CVE-2026-125114 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The conditions filter webhook can be pointed at private or link-local addresses, which bypasses the validateUrlSsrf() protection. The worker sends POST requests to those services and stores the response body in execution details, which the execution details API returns.Source: github.com
Which versions are affected by CVE-2026-125114?
novu: before 3.15.0.Source: cve.now feed data
Am I affected, and how do I check?
Versions before 3.15.0 with a workflow condition step configured with a webhook URL. To check, look at the installed Novu version and review workflows for condition steps that use a webhook URL.Source: github.com
How do I fix CVE-2026-125114?
Upgrade Novu to 3.15.0 or later, the listed fixed version.Source: github.com