@novu/application-generic: validateUrlSsrf permits CGNAT (100.64.0.0/10) destinations — affects Workflow HTTP request step + Webhook filter condition
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (@novu/application-generic 3.17.0), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
- Affected
- < 3.17.0
- Fixed in
- 3.17.0
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-vg6v-j97m-h5xq lists affected ranges: npm @novu/application-generic >=0 <3.17.0
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 6.8 · CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:N/A:N
- EPSS
- No dated EPSS signal available.
Source description
As published by the source; long descriptions are shortened.
Hi Novu team, Reporting an SSRF blocklist gap in the shared validateUrlSsrf guard. A complete self-contained reproduction is inlined below — copy the four files into a directory and run docker compose up, plus a single-file probe that runs against Node directly. Locally validated against HEAD 291817c. Summary Novu's shared SSRF guard validateUrlSsrf(url) is used before server-side requests to user-configured URLs. The guard resolves hostnames and blocks a regex list of private/reserved IP ranges, but it does not block 100.64.0.0/10 shared address space. As a result, Novu features protected by this guard can still send server-side requests to destinations such as 100.100.100.200 (Alibaba Cloud metadata service) and any other service reachable in 100.64.0.0/10. Affected code Guard: - libs/application-generic/src/utils/ssrf-url-validation.ts - isPrivateIp(...) regex list at lines 9-28 - DNS resolution and address validation at lines 55-72 Product call-sites: - Workflow HTTP request…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-vg6v-j97m-h5xq
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: GHSA-vg6v-j97m-h5xq Advisory: @novu/application-generic: `validateUrlSsrf` permits CGNAT (100.64.0.0/10) destinations — affects Workflow HTTP request step + Webhook filter condition IDs: GHSA-vg6v-j97m-h5xq Record: https://patchnext.com/advisories/ghsa-vg6v-j97m-h5xq (revision 1, source checked 26 Oct 2026, 13:00 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 6.8) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: @novu/application-generic 3.17.0. A vendor fix does not mean a deployment is fixed. ## Affected components - npm @novu/application-generic: affected < 3.17.0; fixed in 3.17.0 ## Suggested inspection (read-only) - `npm ls @novu/application-generic --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on @novu/application-generic. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-vg6v-j97m-h5xq (GitHub-reviewed advisory GHSA-vg6v-j97m-h5xq lists affected ranges: npm @novu/application-generic >=0 <3.17.0) Commands are suggestions: review each one before running it.
Loading voting…