Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2026-20223: Authentication Bypass in Cisco Secure Workload Internal REST APIs

Published May 20, 2026 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS10.0Critical · v3.1
EPSS0.83%58th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Cisco Systems
IdentifiersCVE-2026-20223CWE-306 · Missing Authentication for…

CVE-2026-20223 is a critical authentication bypass vulnerability in the internal REST APIs of Cisco Secure Workload Cluster Software. Insufficient request validation and authentication allow an unauthenticated remote attacker to send crafted API requests and access site resources with Site Admin privileges. Successful exploitation permits sensitive information disclosure and unauthorized configuration changes across tenant boundaries. The vulnerability affects on-premises and SaaS deployments regardless of configuration; the web-based management interface is not affected. Affected releases include 3.9 and earlier, 3.10 before 3.10.8.3, and 4.0 before 4.0.3.17. The vulnerability has a CVSS v3.1 base score of 10.0.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Exploitation compromises tenant isolation by allowing Site Admin-level access to sensitive information and configuration controls across tenant boundaries. Unauthorized changes, including changes to microsegmentation policies, could weaken workload isolation and disrupt operations. The vulnerability is rated as having high confidentiality, integrity, and availability impact, with scope extending beyond the vulnerable API component.

Mitigation

If you can’t patch tonight, do this now.

Cisco states that no workaround addresses the vulnerability. Until fixed software is installed, reduce exposure by restricting network access to management APIs to explicitly authorized systems and isolating the management plane from untrusted networks. Monitor API access logs for anomalous unauthenticated requests, cross-tenant access, and unauthorized configuration changes. These measures reduce exposure or improve detection but do not replace patching.

Remediation

Patch, then assume compromise.

Upgrade on-premises Cisco Secure Workload 3.10 deployments to version 3.10.8.3 or a later fixed release, and 4.0 deployments to version 4.0.3.17 or a later fixed release. Deployments running 3.9 or earlier must migrate to a supported fixed release. Cisco has already remediated its hosted SaaS deployments, and SaaS customers require no action.

Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Cisco SystemsSecure Workloadapplication
FAQ

Frequently asked questions

Is CVE-2026-20223 exploited in the wild?
As of Oct 18, 2026, Mallory has no reports of CVE-2026-20223 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-20223?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2026-20223, the earliest disclosed May 22, 2026.
Is there a patch for CVE-2026-20223?
Upgrade on-premises Cisco Secure Workload 3.10 deployments to version 3.10.8.3 or a later fixed release, and 4.0 deployments to version 4.0.3.17 or a later fixed release. Deployments running 3.9 or earlier must migrate to a supported fixed release.
What products are affected by CVE-2026-20223?
Cisco Systems Secure Workload.
How severe is CVE-2026-20223?
CVE-2026-20223 has a CVSS v3.1 score of 10.0 (Critical) and an EPSS score of 0.83% (58th percentile) as of Oct 18, 2026.
Activity feed

Recent activity

69 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+8 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity56Community discussion across Reddit, Mastodon, and other social sources.