CVE-2026-33390
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn Incorrect Privilege Assignment vulnerability was discovered in the synchronization functionality due to Arc sensors receiving CLI permissions. An authenticated user with limited privileges can push administrative CLI commands through the sync, altering the device configuration, and/or affecting its availability.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceAn Incorrect Privilege Assignment vulnerability exists in the synchronization functionality where Arc sensors incorrectly receive CLI permissions. This allows authenticated users with limited privileges to push administrative CLI commands through the sync mechanism, enabling unauthorized configuration changes and potential denial of service.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 26.2.0< 26.2.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed product and versionRun the command to display the Nozomi Networks product version (e.g., 'version', 'show system info', or check the product's about page in the GUI)Affected if The product is Nozominetworks Cmc or Guardian and the version is below 26.2.0
-
Confirm Arc sensor feature is enabledCheck if Arc sensors are configured in the environment - typically found in sensor management settings, device inventory, or sync configuration pagesAffected if Arc sensors are present and the sync functionality is configured to use them
-
Examine sync functionality configurationReview the synchronization settings between central management and distributed sensors - look for sync paths involving Arc sensors and any CLI-related permissionsAffected if The sync mechanism is active and includes Arc sensor synchronization with elevated privileges
-
Inspect user privilege assignmentsCheck the permission model for non-administrative users who have access to the sync functionality - verify if limited-privilege users can trigger sync operationsAffected if Users with limited (non-CLI-admin) privileges have access to the sync mechanism that handles Arc sensors
A user is affected if they run Cmc or Guardian versions below 26.2.0, have Arc sensors configured, and the sync functionality with elevated CLI permissions is enabled for those sensors.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped26.2.0
Restrict CLI permissions for Arc sensors in the sync functionality and implement proper privilege boundaries to prevent authenticated low-privilege users from executing administrative commands.
CMC and Guardian version 26.2.0 or later
- Verify current CMC and Guardian versions by checking the device management interface or running version commands
- Download CMC version 26.2.0 or later from the official Nozomi Networks support portal
- Download Guardian version 26.2.0 or later from the official Nozomi Networks support portal
- Follow the standard Nozomi Networks upgrade procedure for your deployment type (this typically involves uploading the upgrade file through the admin interface or using the CLI upgrade command)
- After upgrade, verify that the version has been successfully updated
- Confirm that the synchronization functionality no longer grants excessive CLI permissions to Arc sensors by testing with a limited-privilege user account
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-33390 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-33390 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data