# CVE-2026-33391: Incorrect authorization in Smart Polling configuration in Guardian/CMC before 26.3.0

> Authenticated low-privilege users can bypass access controls to modify Smart Polling configurations, disrupting asset visibility in Nozomi Networks CMC.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Sep 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-jx7f-4jrv-rjh9

## What is CVE-2026-33391?

CVE-2026-33391 is a medium-severity missing authorization vulnerability in Nozomi Networks CMC, published on 8 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An access control vulnerability was discovered in the Smart Polling configuration functionality due to insufficient validation of user privileges. An authenticated user with limited privileges can remotely bypass the intended access control of the web management interface and modify the Smart Polling discovery configuration. This allows the attacker to disrupt the visibility of assets in the monitored network.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-33391 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-33391 is a medium-severity missing authorization vulnerability in Nozomi Networks CMC, published on 8 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-33391 in the wild and no public exploit code.

Affected product: Nozomi Networks CMC. 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-33391/ (Markdown: https://insights.sbomify.com/CVE-2026-33391/index.md)
```

## Sources

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

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