CVE-2026-20223 remediation guide

Cisco Cisco Secure Workload, secure workload

A vulnerability in the access validation of internal REST APIs of Cisco Secure Workload could allow an unauthenticated, remote attacker to access site resources with the privileges of the Site Admin role. This vulnerability is due to insufficient validation and authentication when accessing REST API endpoints. An attacker could exploit this vulnerability if they are able to send a crafted API request to an affected endpoint. A successful exploit could allow the attacker to read sensitive information and make configuration changes across tenant boundaries with the privileges of the...

Open CVE record

ProductCisco Cisco Secure Workload, secure workload

Affected versions>= 2.2.1.41, >= 3.2.1.18, >= 3.3.2.50, >= 3.4.1.28, >= 3.4.1.34, >= 2.3.1.45, >= 2.3.1.41, >= 3.3.2.28, >= 3.1.1.59, >= 2.0.2.20, >= 2.1.1.33, >= 2.1.1.29, >= 3.2.1.28, >= 3.4.1.35, >= 3.1.1.65, >= 3.1.1.67, >= 2.0.1.34, >= 2.3.1.49, >= 2.2.1.39, >= 3.4.1.19

Fixed versions3.10.8.3, 4.0.3.17

Priority basisReview · CVSS 10 · EPSS 0.83%

Identify the affected asset

Confirm whether Cisco Cisco Secure Workload, secure workload 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.

Validate the affected-version match

Compare the deployed version with the affected range: >= 2.2.1.41, >= 3.2.1.18, >= 3.3.2.50, >= 3.4.1.28, >= 3.4.1.34, >= 2.3.1.45, >= 2.3.1.41, >= 3.3.2.28, >= 3.1.1.59, >= 2.0.2.20, >= 2.1.1.33, >= 2.1.1.29, >= 3.2.1.28, >= 3.4.1.35, >= 3.1.1.65, >= 3.1.1.67, >= 2.0.1.34, >= 2.3.1.49, >= 2.2.1.39, >= 3.4.1.19. Treat incomplete inventory results as unresolved.

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.

Apply supported remediation

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

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.