Actively exploited in the wild
Cisco Catalyst SD-WAN Manager Directory or Path Traversal Vulnerability
Cisco - Catalyst SD-WAN Manager · Listed in the CISA KEV since 2026-06-15. This indicates confirmed attacks in production environments.
Required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
CVE-2026-20262
MediumCVSS 6.5KEVExploitation Probability (EPSS)
Very high risk98th percentile - higher than 98% of all known CVEs
Summary
A vulnerability in the web UI of Cisco Catalyst SD-WAN Manager allows an authenticated remote attacker to create or overwrite any file on the filesystem. This is due to improper input validation during file upload.
Risk Assessment
An attacker could overwrite critical system files, leading to privilege escalation to root and full system compromise.
Recommendation
Update Cisco Catalyst SD-WAN Manager to the latest version and restrict user account privileges to the minimum necessary.
Original NVD description (English source)
A vulnerability in the web UI of Cisco Catalyst SD-WAN Manager, formerly SD-WAN vManage, could allow an authenticated, remote attacker to create a file or overwrite any file on the filesystem of an affected system. This vulnerability exists because the affected software does not properly validate user-supplied input during a file upload process. An attacker could exploit this vulnerability by sending a crafted HTTP request to an affected API endpoint of the affected system. A successful exploit could allow the attacker to create or overwrite any file on the underlying operating system. This file could later be used to elevate to root. To exploit this vulnerability, the attacker must have valid credentials with at least a lower-privileged, single-task user account.

