Novu Security Update Addresses 1 Vulnerability
Tech GuruQuick Answer
Novu CVE-2026-75510 affects the @novu/js In-App Inbox: a notification author or environment API-key holder can store an unsafe redirect that executes script when a recipient clicks it in the browser conditions described by the advisory. The package range is 3.17.0 and earlier; the listed fix is 3.18.0. Check the actual browser bundle, including applications that embed the inbox through a wrapper.
Confirm Scope And Apply The Supported Fix
What to do now: inventory shipped @novu/js copies, notification-author permissions and environment API keys. Update to the supported fixed package, rebuild and redeploy the embedding application, and verify that old vulnerable assets are no longer served. Restricting notification authors is containment, not the package fix.
Source recheck: October 2, 2026 UTC. The linked project advisories were checked for this revision; deployment applicability and successful remediation still require local evidence. Recheck the supported release before changing production.
Scope And Authority
| Product scope | Novu packages and release streams identified in the project advisories |
|---|---|
| Advisory | GHSA-8gr3-5j6f-25gp |
| CVE | CVE-2026-75510 |
| Authoritative release date | 2026-07-08 UTC (project advisory dates, not database ingestion) |
| Authority revision date | 2026-08-18 UTC (project advisory dates, not database ingestion) |
| Affected versions | @novu/js <= 3.17.0 |
| Fixed version | @novu/js 3.18.0 |
| CVSS base score | 5.1 (CVSS v4, GitHub Advisory Database; no score in the primary project JSON) |
| CVSS severity | Medium |
| Exploitation status | Not stated by the authority; no exploitation claim is inferred. |
What Changed
The vulnerable path passes a notification redirect URL into browser navigation without an adequate scheme check. The report describes a v1 workflow and a recipient click in Chromium, with potential access to the receiving application's browser session context. Its 3.15.0 reproduction is evidence reported by the advisory author, not a TechGeeks test or an in-the-wild exploitation report; the structured affected-package range extends through 3.17.0.
What To Validate Now
- Inventory. Find inbox embeddings, dependency lockfiles and served JavaScript assets; record who can author workflows and access each environment API key.
- Establish applicability. Match the deployed
@novu/jsversion to the <= 3.17.0 range. For wrappers such as@novu/react, inspect the resolved inbox dependency rather than assuming identical version numbering. - Remediate. Apply @novu/js 3.18.0 through the supported vendor or project channel, following the current advisory and change-control requirements.
- Validate. Use an isolated test inbox to verify legitimate notification links and rejection of disallowed redirect schemes. Check the deployed asset version and preserve application authentication during testing.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
Use the exact supported release stream and repository. Test dependencies, clusters, integrations, and rollback before broad deployment; a CVSS rating or reachable feature is not evidence of exploitation.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.
