# CVE-2026-75517: Novu access control bypass in integration mutations

Source: https://junglewise.ai/threats/cve-2026-75517-novu-provides-an-api-for-sending-notifications-through-multiple  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-22. Updated: 2026-09-26  
License: CC BY 4.0 with a link back

CVE-2026-75517 · Severity: medium · CVSS 6.5 · Published 2026-09-22

Novu is a notification platform that manages integrations with third-party providers. Before version 3.18.0, users with access to one environment could delete, modify, or reconfigure integrations from other environments within the same organization, potentially compromising notification delivery or exposing provider credentials. The 3.18.0 patch only partially addresses this for API-key authentication while leaving dashboard-session behavior vulnerable.

Technologies: [Novu](https://junglewise.ai/threats/technologies/novu). Vendors: [Novu](https://junglewise.ai/threats/vendors/novu).

## Quick answers

**Is CVE-2026-75517 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-75517 being exploited in the wild.

**How severe is CVE-2026-75517?** Medium severity, with a CVSS score of 6.5, published 22 September 2026.

**Which products and versions are affected?** Novu before 3.18.0.

**Is there a fix for CVE-2026-75517?** A patch was published on 2026-06-09: Version 3.18.0 released with partial fix for API-key authentication only Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-75517 attacked?** It is attacked over the network, in a hosted service.

**Am I affected by CVE-2026-75517?** Check whether you run Novu at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

An access control vulnerability in Novu's integration mutation endpoints (remove-integration, update-integration, auto-configure-integration, set-integration-as-primary) fails to consistently enforce environment boundaries when looking up integrations by integrationId and organizationId. Attackers with API key or session access to one environment can target integration identifiers from other environments in the same organization. Version 3.18.0 scopes environment-key API authentication but deliberately retains cross-environment behavior for dashboard sessions, leaving the remediation incomplete.

## Affected products

- Novu Novu before 3.18.0

## Timeline

- 2026-09-22: disclosed
- 2026-06-09: patched: Version 3.18.0 released with partial fix for API-key authentication only

## References

- [https://github.com/novuhq/novu/commit/3d9bbdccf4e36224b5558c245d2b7c085b5d5302](https://github.com/novuhq/novu/commit/3d9bbdccf4e36224b5558c245d2b7c085b5d5302)
- [https://github.com/novuhq/novu/pull/11480](https://github.com/novuhq/novu/pull/11480)

## Related threats

- [Novu SSRF in HTTP requests and webhooks via RFC6598 addresses](https://junglewise.ai/threats/cve-2026-125115-novu-provides-an-api-for-sending-notifications-through-multiple)
- [Novu improper webhook URL validation in chat providers](https://junglewise.ai/threats/cve-2026-75511-novu-provides-an-api-for-sending-notifications-through-multiple)
- [Novu stored XSS in In-App Inbox via javascript: scheme in redirect URL](https://junglewise.ai/threats/cve-2026-75510-novu-stored-xss-in-in-app-inbox-via-javascript-scheme-in-redirect)