Vulnerabilities in pkg:npm/@novu/api

PACKAGE
Advisory Summary

GHSA-4x48-cgf9-q33f is a HIGH novu has ssrf vulnerability (CWE-918: Server-Side Request Forgery (SSRF)) affecting @novu/api libraries in the npm ecosystem. The issue involves novu has ssrf via conditions filter webhook bypasses validateurlssrf() protection. Remediation is available by upgrading affected packages to version 3.15.0.

1 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:npm/@novu/api

1 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:npm/@novu/api. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-4x48-cgf9-q33f - HIGH Novu has SSRF via conditions filter webhook bypasses validateUrlSsrf() protection

GHSA-4x48-cgf9-q33f at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-4x48-cgf9-q33f
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-918: Server-Side Request Forgery (SSRF)
Affected Product @novu/api
Package Ecosystem npm
Published Date
Last Updated

How to Fix GHSA-4x48-cgf9-q33f

To remediate this vulnerability, upgrade all affected @novu/api dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

@novu/api fixed: 3.15.0
npm install @novu/api@3.15.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls @novu/api

How to Check if You Are Affected

To determine whether your Node.js application is affected by GHSA-4x48-cgf9-q33f, inspect your project dependencies using npm:

npm ls @novu/api

Analyze the terminal output to locate any version of @novu/api in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.15.0), your application is affected.

Note: The npm ls @novu/api command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-918: Server-Side Request Forgery (SSRF), where the web server receives a url or similar request from an upstream component and retrieves the contents of this url, but it does not sufficiently ensure that the request is being sent to the expected destination. In @novu/api, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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

GHSA-4x48-cgf9-q33f Affected @novu/api Versions

1 component(s)
Fixed Versions:
3.15.0
Product / Package Ecosystem Affected Versions Fixed Version
@novu/api
npm
< 3.15.0
3.15.0

References

Frequently Asked Questions

What is GHSA-4x48-cgf9-q33f?
GHSA-4x48-cgf9-q33f is a security vulnerability in @novu/api involving Novu has SSRF via conditions filter webhook bypasses validateUrlSsrf() protection under CWE-918: Server-Side Request Forgery (SSRF).
Which @novu/api versions are affected?
Affected versions include releases prior to 3.15.0 across affected packages: @novu/api.
What version fixes GHSA-4x48-cgf9-q33f?
Upgrading to 3.15.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is @novu/api affected?
Yes, @novu/api is affected in releases prior to 3.15.0. Upgrade your dependency to 3.15.0 or later.
What CWE is associated with GHSA-4x48-cgf9-q33f?
GHSA-4x48-cgf9-q33f is classified under CWE-918: Server-Side Request Forgery (SSRF) (The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.).
How can I check npm dependencies for GHSA-4x48-cgf9-q33f?
Run the dependency tree command: 'npm ls @novu/api'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-4x48-cgf9-q33f",
  "modified" : "2026-04-14T23:22:48Z",
  "published" : "2026-04-14T23:22:48Z",
  "aliases" : [ ],
  "summary" : "Novu has SSRF via conditions filter webhook bypasses validateUrlSsrf() protection",
  "details" : "## Summary\n\nThe 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.\n\n## Root Cause\n\n`conditions-filter.usecase.ts` line 261:\n```typescript\nreturn await axios.post(child.webhookUrl, payload, config).then((response) => {\n  return response.data as Record<string, unknown>;\n});\n```\n\nNo call to `validateUrlSsrf()`. The `webhookUrl` comes from the workflow condition configuration with zero validation.\n\n## Protected Code (for contrast)\n\n`execute-http-request-step.usecase.ts` line 130:\n```typescript\nconst ssrfValidationError = await validateUrlSsrf(url);\nif (ssrfValidationError) {\n  // blocked\n}\n```\n\nThis 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.\n\n## Proof of Concept\n\n1. Create a workflow with a condition step\n2. Configure the condition's webhook URL to `http://169.254.169.254/latest/meta-data/iam/security-credentials/`\n3. Trigger the workflow by sending a notification event\n4. The worker evaluates the condition and calls `axios.post()` to the metadata endpoint\n5. The response data is stored in execution details and accessible via the execution details API\n\n## Impact\n\nFull-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.\n\nThe 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.\n\n## Suggested Fix\n\nExtract `validateUrlSsrf()` to a shared utility and call it before the axios.post in conditions-filter.usecase.ts:\n\n```typescript\nconst ssrfError = await validateUrlSsrf(child.webhookUrl);\nif (ssrfError) {\n  throw new Error('Webhook URL blocked by SSRF protection');\n}\nreturn await axios.post(child.webhookUrl, payload, config)...\n```",
  "severity" : [ ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@novu/api"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "3.15.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/novuhq/novu/security/advisories/GHSA-4x48-cgf9-q33f"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/novuhq/novu/commit/87d965eb88340ac7cd262dd52c8015acd092dc68"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/novuhq/novu"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-918" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-04-14T23:22:48Z",
    "nvd_published_at" : null
  }
}