CVE-2026-20245: Cisco Catalyst SD-WAN authenticated root privilege escalation

Quick Answer

CISA added CVE-2026-20245 to its Known Exploited Vulnerabilities catalog on 2026-06-09, confirming that exploitation has occurred. If you operate Cisco Catalyst SD-WAN Manager, identify the exact version and relevant configuration now, preserve security evidence, and follow the live vendor remediation. A KEV match does not prove your system was compromised, and installing an update does not rule out earlier exploitation.

Last verified: 2026-09-17 UTC. CISA KEV snapshot version 2026.09.16. Recheck the live advisory before changing production.

Context

Status At A Glance

Product scope	Cisco — Catalyst SD-WAN Manager
CVE	CVE-2026-20245
TechGeeks response tier	P0 — confirm an exact match and act now
CISA KEV added	2026-06-09
Vendor severity	High
CVSS	CVSS 3.1 base 7.8 — CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Ransomware field	Unknown — this is not the same as No; CISA has not marked the field Known.
Forensic-triage field	No in the current CISA field; organizations should still investigate when exposure or evidence warrants it.
CWE	CWE-116
Federal remediation date	2026-06-23 — applies to covered federal agencies; other organizations should set a risk-based deadline.

What Happened

Cisco Catalyst SD-WAN Manager Improper Encoding or Escaping of Output Vulnerability. Cisco Catalyst SD-WAN Manager formerly SD-WAN vManage contains an improper encoding or escaping of output vulnerability. This vulnerability could allow an authenticated, local attacker to execute arbitrary commands as root by supplying a crafted file to the affected system. CISA's KEV listing confirms exploitation evidence, but it does not state how widespread the activity is or prove that any particular installation was compromised.

Affected Scope

Cisco Catalyst SD-WAN Controller, Manager, and Validator in all deployment types are affected regardless of configuration. Exploitation requires netadmin privileges, obtained through valid credentials or a separate authentication-bypass path.

Match the exact edition, hardware or virtual platform, release, patch level, enabled feature, and management exposure. A product-family name alone is not enough to establish applicability.

Steps

What To Do Now

1. Confirm. Inventory every Catalyst SD-WAN Manager asset and record its exact version, patch level, role, relevant configuration, and exposure.
2. Preserve. Save UTC timestamps, off-device authentication, firewall, proxy, DNS, endpoint, application, and SIEM evidence before logs rotate or a disruptive change removes context.
3. Contain. Restrict unnecessary internet and management-plane access using supported controls. Follow the live advisory: Open the live Cisco advisory.
4. Remediate. Before upgrading, collect admin-tech and relevant logs from each control component. Upgrade to the fixed release, inspect Cisco's indicators, verify edge-device configuration, and contact TAC if compromise is confirmed.
5. Validate. Verify the resulting version or patch level, service health, logging, expected access, an expected denial, and representative dependent workflows.
6. Escalate. If exposure overlapped the vulnerable period or evidence is suspicious, treat the system as a potential incident and follow vendor and incident-response recovery guidance.

Fixed Releases And Mitigation

Verified fixed release, patch level, or update guidance captured at the last check:

• 20.9.9.2
• 20.12.7.2
• 20.15.4.5
• 20.15.5.3
• 20.18.3.1
• 26.1.1.2

Mitigation boundary: Cisco provides a Live Protect shield as temporary partial protection, with documented disaster-recovery and cluster restrictions. It is not remediation; upgrade is required.

A workaround, access restriction, or provider-side control reduces a described path; it does not necessarily remove vulnerable code or erase compromise.

Investigation And Recovery

Cisco observed cases where exploitation resulted in configuration changes pushed to edge devices. Preserve logs/admin-tech before upgrading and verify the fabric and edge configuration afterward.

When an attacker may have gained administrative, root, SYSTEM, identity, management-plane, or code-execution access, patching alone is not an eradication claim. Preserve evidence, scope affected accounts and downstream systems, rotate exposed credentials or certificates when justified, and rebuild from a trusted source when vendor or incident-response guidance requires it.

Notes

Exploitation Evidence

Vendor statement: In June 2026, Cisco PSIRT became aware of exploitation; Cisco says successful exploitation by other methods than valid/netadmin credentials or CVE-2026-20182/CVE-2026-20127 is not known.

CISA statement: CVE-2026-20245 was added to KEV on 2026-06-09. The ransomware field is Unknown, and the forensic-triage field is No. These are separate signals.

Validation And Boundaries

This notice does not prove that every product carrying the family name is affected, that exploitation is widespread, that a clean indicator search rules out compromise, or that a successful update restored trust. TechGeeks has not reproduced the exploit and does not replace the vendor advisory, asset inventory, vulnerability scanner, or incident-response process.

Related TechGeeks Resources

• Security Hot Page
• All Security Notices
• What to Do When a Device Hits CISA KEV
• Router CVE Exposure, Version, and Mitigation Checklist
• IoT Firmware Update and End-of-Support Checklist
• Live Protect and Runtime Vulnerability Shielding

References

• Cisco advisory or support notice
• NVD CVE record
• CISA source

Wrap-Up

Record whether CVE-2026-20245 applies to your environment. If it does, assign an owner, preserve the change and investigation evidence, complete the vendor action, and document the validated result.

Correction policy: If a primary source changes affected versions, remediation, exploitation status, or recovery guidance, TechGeeks will update this page and its verification date.