CVE-2026-75510
MediumCVSS 5.1Summary
Novu before version 3.18.0 accepts notification redirect URLs without validating the URL scheme, allowing javascript: in the redirect attribute. When a recipient clicks the notification, JavaScript can execute in the app context, potentially exposing session data.
Risk Assessment
Risk of session hijacking or unauthorized actions in the customer application or Novu dashboard, especially in Chromium-based browsers.
Recommendation
Upgrade Novu to version 3.18.0, which restricts URL schemes in notification redirects.
Other vulnerabilities in Novu
See all- CVE-2026-75517Medium
In Novu prior to 3.18.0, integration mutation use cases including remove-integration, update-integration, auto-configure-integration, and set-integration-as-primary look up an integration by integrationId and organizationId without consistently enforcing environmentId. A caller with access to one environment in an organization can target an integration identifier from another environment and delete the integration, modify its credentials, change the primary provider, or trigger auto-configuration. The repository advisory defines both environment API keys and dashboard sessions as affected. The 3.18.0 change enforces the environment boundary only for environment-scoped API-key authentication, while its tests intentionally retain cross-environment dashboard-session behavior, so it does not completely remediate the advisory-defined scope. Version 3.18.0 is a partial fix attempt, and the dashboard-session behavior requires curator resolution.
- CVE-2026-75511Medium
Novu before version 3.18.0 does not validate chat webhook URLs from various sources, passing them to raw HTTP requests. An authenticated user can send POST requests to internal network services, potentially causing unauthorized actions.
Original NVD description (English source)
Novu provides an API for sending notifications through multiple channels. Prior to 3.18.0, Novu's @novu/js In-App Inbox and the @novu/react Inbox component accept a notification call-to-action redirect.url from the v1 cta.data object and pass it through apps/api/src/app/inbox/utils/notification-mapper.ts and packages/js/src/ui/components/Notification/DefaultNotification.tsx to the navigate function in packages/js/src/ui/context/InboxContext.tsx without validating its URL scheme. An authenticated organization member or environment API-key holder can store a javascript: redirect with target _self in an in-app workflow. When a recipient using a Chromium-based browser clicks the notification, window.open executes the redirect in the current inbox-hosting origin, which can expose session material and permit authenticated actions in a customer application or the self-hosted Novu dashboard. This issue is fixed in version 3.18.0.