Catalyst Sd Wan ManagerApplication · Cisco
CVE-2026-20209
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 web UI of Cisco Catalyst SD-WAN Manager, formerly SD-WAN vManage, could allow an authenticated, remote attacker with read-only permissions to elevate their privileges from low to high and perform actions as a high-privileged user. This vulnerability exists because sensitive session information is recorded in audit logs. An attacker could exploit this vulnerability by elevating their read-only permissions in Cisco Catalyst SD-WAN Manager to those of a high-privileged user. A successful exploit could allow the attacker to perform actions as a high-privileged 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 confidenceThe vulnerability exists in Cisco Catalyst SD-WAN Manager's web UI where sensitive session information is improperly recorded in audit logs. An authenticated attacker with read-only permissions can access this session data in the logs to elevate their privileges to those of a high-privileged user, allowing them to perform actions beyond their authorized access level.
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.9.1>= 20.10, < 20.12.5.4>= 20.12.6, < 20.12.6.2>= 20.13, < 20.15.4.4>= 20.15.5, < 20.15.5.2>= 20.16, < 20.18.2.2>= 26.1, < 26.1.1.1= 20.12.7CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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 versionAccess the web UI and navigate to Administration > Settings > Software Version, or use the CLI command 'show version' via console/SSH to retrieve the installed software versionAffected if The installed version falls into any of these ranges: < 20.9.9.1; >= 20.10 and < 20.12.5.4; = 20.12.7; >= 20.12.6 and < 20.12.6.2; >= 20.13 and < 20.15.4.4; >= 20.15.5 and < 20.15.5.2; >= 20.16 and < 20.18.2.2; >= 26.1 and < 26.1.1.1
-
Verify web UI is accessibleAttempt to reach the Cisco Catalyst SD-WAN Manager web interface via HTTPS at the configured management IP addressAffected if The web UI is exposed and accessible to authenticated users
-
Confirm audit logging is enabledNavigate to Administration > Audit Logs in the web UI, or check the system logging configuration via CLI with 'show logging' or 'show audit-logs'Affected if Audit logging is turned on and storing log entries
-
Inspect audit logs for sensitive session dataReview recent audit log entries, looking for session tokens, cookies, authentication credentials, or session identifiers that should not be recorded in plaintextAffected if Audit logs contain any sensitive session information such as session tokens, authentication tokens, or session cookies in plaintext
The environment is affected if the installed version matches any of the vulnerable version ranges AND audit logging is enabled, allowing low-privilege users to potentially view session data that could be used for privilege escalation.
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.9.120.12.5.420.12.6.2
Apply the Cisco vendor patch when available. In the interim, monitor audit logs for suspicious privilege escalation activity and consider restricting access to audit log data for low-privilege users.
Upgrade to 20.15.4.4 or later (or the appropriate minimum fixed version for your branch: 20.9.9.1, 20.12.5.4, or 20.12.6.2)
- 1. Identify the currently installed Cisco Catalyst SD-WAN Manager version using 'show version' or via the web UI dashboard.
- 2. Determine which version range your current installation falls into based on the affected versions list.
- 3. For versions < 20.9.9.1: Upgrade to version 20.9.9.1 or later.
- 4. For versions >= 20.10 and < 20.12.5.4: Upgrade to version 20.12.5.4 or later.
- 5. For versions >= 20.12.6 and < 20.12.6.2: Upgrade to version 20.12.6.2 or later.
- 6. For versions >= 20.13 and < 20.15.4.4: Upgrade to version 20.15.4.4 or later.
- 7. After upgrade, verify the fix by checking that audit logs no longer contain sensitive session information (session tokens, cookies).
- 8. Test that read-only users cannot escalate privileges using the fixed version.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Catalyst Sd Wan Manager
Scoped from the published advisory
- 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-20209 — 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-20209 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