Novu: SSRF via conditions filter webhook bypasses validateUrlSsrf() protection
cve-program · CVE-2026-125114
PublishedNovu 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.
Read the publisher's advisoryeuvd · EUVD-2026-120495
PublishedNovu 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.
Read the publisher's advisorynvd · CVE-2026-125114
PublishedNovu 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.
Read the publisher's advisoryosv · GHSA-4x48-cgf9-q33f
Published## Summary The conditions filter webhook at `libs/application-generic/src/usecases/conditions-filter/conditions-filter.usecase.ts` line 261 sends POST requests to user-configured URLs using raw `axios.post()` with no SSRF validation. The HTTP Request workflow step in the same codebase correctly uses `validateUrlSsrf()` which blocks private IP ranges. The conditions webhook was not included in this protection. ## Root Cause `conditions-filter.usecase.ts` line 261: ```typescript return await axios.post(child.webhookUrl, payload, config).then((response) => { return response.data as Record<string, unknown>; }); ``` No call to `validateUrlSsrf()`. The `webhookUrl` comes from the workflow condition configuration with zero validation. ## Protected Code (for contrast) `execute-http-request-step.usecase.ts` line 130: ```typescript const ssrfValidationError = await validateUrlSsrf(url); if (ssrfValidationError) { // blocked } ``` This function resolves DNS and checks against private ranges (127.0.0.0/8, 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16, 169.254.0.0/16). It exists in the codebase but is not applied to the conditions webhook path. ## Proof of Concept 1. Create a workflow with a condition step 2. Configure the condition's webhook URL to `http://169.254.169.254/latest/meta-data/iam/security-credentials/` 3. Trigger the workflow by sending a notification event 4. The worker evaluates the condition and calls `axios.post()` to the metadata endpoint 5. The response data is stored in execution details and accessible via the execution details API ## Impact Full-read SSRF. The response body is returned as `Record<string, unknown>` for condition evaluation and stored in the execution details `raw` field. The `GET /execution-details` API returns this data. The POST method limits some metadata endpoints (GCP requires GET, Azure requires GET), but AWS IMDSv1 accepts POST and returns credentials. Internal services accepting POST are also reachable. ## Suggested Fix Extract `validateUrlSsrf()` to a shared utility and call it before the axios.post in conditions-filter.usecase.ts: ```typescript const ssrfError = await validateUrlSsrf(child.webhookUrl); if (ssrfError) { throw new Error('Webhook URL blocked by SSRF protection'); } return await axios.post(child.webhookUrl, payload, config)... ```
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2026-125114 · CVE overview and exploitation status
cve-program · CVE-2026-125114
- https://github.com/novuhq/novu/security/advisories/GHSA-4x48-cgf9-q33f
- https://github.com/novuhq/novu/pull/10457
- https://github.com/novuhq/novu/commit/87d965eb88340ac7cd262dd52c8015acd092dc68
- https://github.com/novuhq/novu/releases/tag/v3.15.0
euvd · EUVD-2026-120495
- https://github.com/novuhq/novu/security/advisories/GHSA-4x48-cgf9-q33f
- https://github.com/novuhq/novu/pull/10457
- https://github.com/novuhq/novu/commit/87d965eb88340ac7cd262dd52c8015acd092dc68
- https://github.com/novuhq/novu/releases/tag/v3.15.0
nvd · CVE-2026-125114
- https://github.com/novuhq/novu/commit/87d965eb88340ac7cd262dd52c8015acd092dc68
- https://github.com/novuhq/novu/pull/10457
- https://github.com/novuhq/novu/releases/tag/v3.15.0
- https://github.com/novuhq/novu/security/advisories/GHSA-4x48-cgf9-q33f
osv · GHSA-4x48-cgf9-q33f
Related changes
Linked by CVE identifier- Novu: SSRF via conditions filter webhook bypasses validateUrlSsrf() protection · Newly collected advisory · 10 Nov 2026
- Novu has SSRF via conditions filter webhook bypasses validateUrlSsrf() protection · Advisory content revised · 9 Nov 2026