dbcve.org
CmcApplication · Nozominetworks

CVE-2026-31983

MEDIUM · 5.3 CVSS v3.1 Published 2026-07-09
Fix available
A fix is available. Upgrade to 26.2.0 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 6 weeks old

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 · unedited
A Missing Authentication vulnerability was discovered in the SSH keys synchronization endpoint. An unauthenticated attacker can send a request to the SSH keys synchronization endpoint and obtain the list of users that have uploaded their public SSH keys, their groups, and the uploaded public SSH keys.

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 · high confidence

The SSH keys synchronization endpoint lacks authentication controls, allowing any unauthenticated requester to retrieve sensitive information including usernames, group memberships, and public SSH keys associated with users in the system.

MitigationImplement proper authentication and authorization checks on the SSH keys synchronization endpoint to ensure only authenticated and authorized users can access user data and SSH public keys.

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
CmcApplication
Affected:< 26.2.0
GuardianApplication
Affected:< 26.2.0

CVSS 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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed Nozomi product
    Run 'version' or 'system info' command, or check the web UI footer for the product name (CMC or Guardian)
    Affected if The product is Nozomi Networks CMC or Guardian
  2. Check the installed version number
    Run 'version' command or check the web UI for the exact version number
    Affected if The version is less than 26.2.0 (for example, 26.1.x, 26.0.x, etc.)
  3. Locate the SSH keys synchronization endpoint
    Identify the API endpoint path - typically something like /api/ssh-keys or /sync/ssh-keys - by reviewing API documentation or network traffic
    Affected if The endpoint exists and is accessible on the system
  4. Test unauthenticated access to the endpoint
    Send an HTTP GET request to the SSH keys synchronization endpoint without providing any authentication credentials (no session cookie, no API key, no Authorization header)
    Affected if The request returns HTTP 200 with user data, usernames, group memberships, or SSH public keys without requiring authentication

A user is affected if they run Nozomi Networks CMC or Guardian with a version lower than 26.2.0 and the SSH keys synchronization endpoint responds to unauthenticated requests with sensitive user data.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 26.2.0 or later
Fixed in 26.2.0
Interim mitigation

Implement proper authentication and authorization checks on the SSH keys synchronization endpoint to ensure only authenticated and authorized users can access user data and SSH public keys.

Recommended fix High confidence

26.2.0

  1. 1. Review the product release notes for version 26.2.0 to understand changes and any known migration requirements
  2. 2. Create a full backup of the current CMC and/or Guardian configuration
  3. 3. Download the version 26.2.0 (or later) installation package from the official vendor source
  4. 4. Upgrade CMC to version 26.2.0 or later following the vendor's documented upgrade procedure
  5. 5. Upgrade Guardian to version 26.2.0 or later following the vendor's documented upgrade procedure
  6. 6. After upgrade, verify the SSH keys synchronization endpoint now requires authentication
  7. 7. Test that legitimate users can still access and manage their SSH keys
Caveat Review vendor release notes for version 26.2.0 for any breaking changes or required migration steps before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cmc Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-31983 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-31983 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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