# CVE-2026-78328: Missing authorization in Network Security Manager (NSM)

> A lower-privileged Admin user can escalate privileges to SuperAdmin in SonicWall NSM due to missing authorization checks.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/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:** 4 Sep 2026
- **Updated:** 4 Sep 2026
- **Also known as:** GHSA-h2gj-x3qg-39wj

## What is CVE-2026-78328?

CVE-2026-78328 is a critical missing authorization vulnerability in SonicWall Network Security Manager (NSM), published on 4 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A missing authorization vulnerability in the SonicWall Network Security Manager (NSM) On-Prem Management interface allows a lower-privileged Admin user to escalate privileges to SuperAdmin.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-78328 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-78328 is a critical missing authorization vulnerability in SonicWall Network Security Manager (NSM), published on 4 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-78328 in the wild and no public exploit code.

Affected product: SonicWall Network Security Manager (NSM). 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-78328/ (Markdown: https://insights.sbomify.com/CVE-2026-78328/index.md)
```

## Sources

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

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