# CVE-2026-75517: Novu: Cross-Environment Integration Manipulation (IDOR)

> Attackers can manipulate integrations across environments by bypassing environment checks, allowing unauthorized modification or deletion of notification settings.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Sep 2026
- **Updated:** 22 Sep 2026
- **Also known as:** GHSA-jh6r-hjhp-wh2h

## What is CVE-2026-75517?

CVE-2026-75517 is a medium-severity missing authorization vulnerability in @novu api-service, published on 22 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Novu provides an API for sending notifications through multiple channels. Prior to 3.18.0, Novu 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.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-75517?


## How do I fix CVE-2026-75517?

No fix has been published for CVE-2026-75517 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-75517 being exploited?

There is no known exploitation of CVE-2026-75517 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-75517 and fix it if it is affected.

What it is: CVE-2026-75517 is a medium-severity missing authorization vulnerability in @novu api-service, published on 22 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-75517 in the wild and no public exploit code.

Affected product: @novu api-service. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-75517/ (Markdown: https://insights.sbomify.com/CVE-2026-75517/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-75517
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-75517
- OSV: https://osv.dev/vulnerability/CVE-2026-75517

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-75517/
Summaries are generated and may contain mistakes; the official description above is the record.