CVE-2026-75510

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.

• https://github.com/novuhq/novu/commit/f105f3d41a4405a75f803634d49f15a967524d8a
• https://github.com/novuhq/novu/pull/11453
• https://github.com/novuhq/novu/releases/tag/v3.18.0
• https://github.com/novuhq/novu/security/advisories/GHSA-8gr3-5j6f-25gp
• https://github.com/novuhq/novu/security/advisories/GHSA-8gr3-5j6f-25gp