CVE REMEDIATION GUIDE
CISA KEV · Known exploitedCriticalFixed-version data available

CVE-2026-20045 remediation guide

Cisco Unified Communications Manager

A vulnerability in Cisco Unified Communications Manager (Unified CM), Cisco Unified Communications Manager Session Management Edition (Unified CM SME), Cisco Unified Communications Manager IM & Presence Service (Unified CM IM&P), Cisco Unity Connection, and Cisco Webex Calling Dedicated Instance could allow an unauthenticated, remote attacker to execute arbitrary commands on the underlying operating system of an affected device.  This vulnerability is due to improper validation of user-supplied input in HTTP requests. An attacker could exploit this vulnerability by sending a se...

Open CVE record
ProductCisco Unified Communications Manager
Affected versions12.5(1)SU2, 12.5(1)SU1, 12.5(1), 12.5(1)SU3, 12.5(1)SU4, 14, 12.5(1)SU5, 14SU1, 12.5(1)SU6, 14SU2, 12.5(1)SU7, 12.5(1)SU7a, 14SU3, 12.5(1)SU8, 12.5(1)SU8a, 15, 15SU1, 14SU4, 14SU4a, 15SU1a
Fixed versions14su5
Priority basisImmediate · CVSS 9.8 · EPSS 4.31%
01

Identify the affected asset

Confirm whether Cisco Unified Communications Manager 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: 12.5(1)SU2, 12.5(1)SU1, 12.5(1), 12.5(1)SU3, 12.5(1)SU4, 14, 12.5(1)SU5, 14SU1, 12.5(1)SU6, 14SU2, 12.5(1)SU7, 12.5(1)SU7a, 14SU3, 12.5(1)SU8, 12.5(1)SU8a, 15, 15SU1, 14SU4, 14SU4a, 15SU1a. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

CISA has listed this vulnerability in the Known Exploited Vulnerabilities catalog. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

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.