Secure WorkloadApplication · Cisco
CVE-2026-20223
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 · uneditedA 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 Site Admin user.
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 confidenceCisco Secure Workload contains an authentication bypass vulnerability in internal REST API endpoints. An unauthenticated remote attacker can send specially crafted API requests to bypass access validation and obtain Site Admin privileges, enabling them to read sensitive data and modify configurations across tenant boundaries.
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
Secure WorkloadApplication
< 3.10.8.3>= 4.0, < 4.0.3.17CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Cisco Secure Workload versionAccess the appliance management interface or use the CLI command to retrieve the current software version (typically via 'show version' or similar administrative tool)Affected if The installed version is lower than 3.10.8.3, or is 4.0.x up to but not including 4.0.3.17
-
Determine if internal REST API is network-exposedReview network segmentation, firewall rules, and access control lists to check whether the internal REST API endpoints are reachable from untrusted or external networksAffected if The internal REST API endpoints are accessible from networks outside the trusted administrative zone
-
Audit for unauthorized Site Admin accountsReview the user management section of the administrative console to list all accounts with Site Admin privileges, looking for unexpected or newly created administrator accountsAffected if Unexpected administrator accounts exist or accounts were created without authorized administrative action
-
Review API access logs for authentication bypass indicatorsExamine API request logs and authentication audit trails for requests that successfully accessed privileged endpoints without proper credentials or with anomalous authorization tokensAffected if Logs show API calls to privileged endpoints originating from unauthenticated sources or showing successful authentication without proper credential validation
A user is affected if their Cisco Secure Workload version falls within the vulnerable ranges AND the internal REST API is network-accessible from untrusted sources.
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.10.8.34.0.3.17
Apply Cisco's official patch for CVE-2026-20223 immediately. Until patched, restrict network access to affected API endpoints and monitor for anomalous API traffic.
Upgrade to Secure Workload 3.10.8.3 or later (3.x line), or 4.0.3.17 or later (4.x line)
- 1. Identify the currently installed Cisco Secure Workload version by navigating to the administration console or checking system documentation
- 2. If running version < 3.10.8.3, plan an upgrade to version 3.10.8.3 or later in the 3.x release line
- 3. If running version 4.0.x (where x < 3.17), plan an upgrade to version 4.0.3.17 or later in the 4.x release line
- 4. Review Cisco upgrade documentation and release notes for the target version before proceeding
- 5. Schedule a maintenance window appropriate for the upgrade given the critical severity
- 6. Perform the upgrade following Cisco's standard upgrade procedures for Secure Workload
- 7. After upgrade, verify the Secure Workload version reflects the patched release
- 8. Validate that the REST API access controls are functioning correctly and confirm the vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Secure Workload
Scoped from the published advisory
- Consultation8.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,784.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-20223 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-20223 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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