CVE REMEDIATION GUIDE
Review reviewCriticalFixed-version data available

CVE-2026-20160 remediation guide

Cisco Cisco Smart Software Manager On-Prem, smart software manager on-prem

A vulnerability in Cisco Smart Software Manager On-Prem (SSM On-Prem) could allow an unauthenticated, remote attacker to execute arbitrary commands on the underlying operating system of an affected SSM On-Prem host. This vulnerability is due to the unintentional exposure of an internal service. An attacker could exploit this vulnerability by sending a crafted request to the API of the exposed service. A successful exploit could allow the attacker to execute commands on the underlying operating system with root-level privileges.

Open CVE record
ProductCisco Cisco Smart Software Manager On-Prem, smart software manager on-prem
Affected versions9-202502, 9-202504, 9-202507, 9-202510, >= 9-202502 < 9-202601
Fixed versions9-202601
Priority basisReview · CVSS 9.8 · EPSS 0.91%
01

Identify the affected asset

Confirm whether Cisco Cisco Smart Software Manager On-Prem, smart software manager on-prem is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: 9-202502, 9-202504, 9-202507, 9-202510, >= 9-202502 < 9-202601. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

The CVSS severity warrants an early asset and exposure review. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Follow the vendor advisory or supported update path. Current fixed-version status: 9-202601. Preserve configuration and rollback material before change.

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.