Catalyst Sd Wan ManagerApplication · Cisco
CVE-2026-20133
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 Cisco Catalyst SD-WAN Software could allow an unauthenticated, remote attacker to view sensitive information on an affected system. This vulnerability is due to insufficient file system restrictions. An authenticated attacker with netadmin privileges could exploit this vulnerability by accessing the vshell of an affected system. A successful exploit could allow the attacker to read sensitive information on the underlying operating system.
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 · moderate confidenceThis vulnerability in Cisco Catalyst SD-WAN Software stems from insufficient file system restrictions that allow an authenticated attacker with netadmin privileges to access the vshell and read sensitive information from the underlying operating system. The attack requires valid credentials with netadmin-level access, making it less accessible than purely unauthenticated flaws but still a significant information disclosure risk.
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
Catalyst Sd Wan ManagerApplication
< 20.9.8.2>= 20.10, < 20.12.5.3>= 20.13, < 20.15.4.2>= 20.16, < 20.18.2.1= 20.12.6CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 Catalyst SD-WAN Manager versionRun 'show version' or check the administration UI for the software version numberAffected if The installed version matches one of the vulnerable ranges: < 20.9.8.2, 20.10.x through < 20.12.5.3, 20.13.x through < 20.15.4.2, 20.16.x through < 20.18.2.1, or exactly 20.12.6
-
Verify if netadmin role users existCheck user accounts in the SD-WAN Manager administration panel or query user role assignments via CLI with 'show users' or similar admin commandsAffected if Any user account is assigned the netadmin role
-
Confirm vshell feature is accessibleAttempt to access the vshell interface or check configuration for vshell availability via CLI or admin consoleAffected if The vshell functionality is enabled and accessible to netadmin users
You are affected if your Cisco Catalyst SD-WAN Manager runs a version within the listed vulnerable ranges AND has users with netadmin privileges who can access the vshell interface.
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 · scoped20.9.8.220.12.5.320.15.4.2
Apply the vendor-supplied patch or update to Cisco Catalyst SD-WAN Software when available, and restrict vshell access to only absolutely necessary personnel with netadmin privileges while implementing least-privilege access controls.
20.9.8.2 (or 20.12.5.3, 20.15.4.2, or 20.18.2.1 depending on your release branch - choose the lowest fixed version in your branch)
- 1. Identify the current installed version of Cisco Catalyst SD-WAN Manager using the administrative interface or CLI
- 2. Determine which version branch (20.9, 20.10-20.12, 20.13-20.15, or 20.16-20.18) the current installation belongs to
- 3. For version < 20.9: upgrade to 20.9.8.2 or later
- 4. For version 20.10-20.12: upgrade to 20.12.5.3 or later
- 5. For version 20.13-20.15: upgrade to 20.15.4.2 or later
- 6. For version 20.16-20.18: upgrade to 20.18.2.1 or later
- 7. After upgrade, verify the version change was successful
- 8. Test that the vshell functionality works as expected with proper file system restrictions in place
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Catalyst Sd Wan Manager
Exploited in the wild — priority engagement
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-20133 — 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-20133 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