CVE-2026-20262 – Medium Severity File Write in Cisco Catalyst SD‑WAN Manager

Key takeaways

  • CVE-2026-20262 is a Medium severity file‑write flaw (CVSS 6.5) in the web UI of Cisco Catalyst SD‑WAN Manager.
  • An authenticated attacker with a low‑privileged account can create or overwrite any file on the underlying OS, paving the way to root.
  • Active exploitation is confirmed in the wild and the issue is listed in the CISA KEV catalog.
  • Patch releases are available for all supported versions; deploy immediately.
  • Monitor for suspicious file‑upload activity (e.g., WAR files, path‑traversal patterns) in manager logs.

Overview

Cisco’s Product Security Incident Response Team (PSIRT) disclosed that a flaw in the web UI of Cisco Catalyst SD‑WAN Manager (formerly vManage) is being actively exploited. The vulnerability, tracked as CVE-2026-20262, allows an attacker who has valid credentials – even a low‑privileged, single‑task user – to upload a crafted file and write it to an arbitrary location on the device’s filesystem. Successful exploitation can lead to arbitrary code execution and privilege escalation to root.

Technical Details

  • Root cause: The file‑upload API does not properly sanitize the supplied filename. Path‑traversal sequences (../) are accepted, enabling an attacker to place files outside the intended upload directory.
  • Attack vector: Remote, network‑accessible (AV:N). Requires authentication with at least a low‑privileged account (PR:L). No user interaction (UI:N). The vulnerability impacts the integrity of the system (I:H) but not confidentiality or availability directly.
  • Typical exploitation flow:
    1. Attacker obtains valid credentials (e.g., via credential stuffing or insider compromise).
    2. Sends a crafted HTTP POST request to the file‑upload endpoint, embedding a path‑traversal payload.
    3. The malicious file (often a WAR archive) is written to a privileged directory such as standalone/deployments/, where it is automatically deployed by the underlying WildFly application server, granting code execution as root.

Example request (truncated for brevity):

POST /api/v1/file-upload HTTP/1.1
Host: sdwan-manager.example.com
Authorization: Basic <base64‑credentials>
Content-Type: multipart/form-data; boundary=----WebKitFormBoundary

------WebKitFormBoundary
Content-Disposition: form-data; name="file"; filename="../../../../var/lib/wildfly/standalone/deployments/malicious.war"
Content-Type: application/octet-stream

<binary payload>
------WebKitFormBoundary--

Log artifacts often show entries like:

/var/log/nms/vmanage-server.log: ../../../../var/lib/wildfly/standalone/deployments/malicious.war

Severity & Impact

MetricValue
CVECVE-2026-20262
VendorCisco
ProductCatalyst SD‑WAN Manager
CVSS6.5 (Medium)
VectorAV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
CWECWE-22 (Path Traversal)
ExploitedYes – active exploitation
CISA KEVCISA KEV

The primary impact is integrity – an attacker can write arbitrary files, which can be leveraged for privilege escalation to root. While confidentiality and availability are not directly affected, the ability to execute code as root makes the overall risk high for any organization running the affected component.

Affected Products

The flaw affects Cisco Catalyst SD‑WAN Manager (on‑prem, Cloud‑Pro, Cloud‑Managed, and FedRAMP‑Government deployments) in versions prior to the security‑only releases:

  • 20.9.9.1, 20.12.7.1, 20.15.4.4, 20.15.5.2, 20.18.3, 26.1.1.1

Patched versions are:

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

For the complete list of affected versions and detailed CPE data, see the CVE page.

Actionable Insights

  • Version inventory: Identify every instance of Catalyst SD‑WAN Manager in your environment and record its firmware version.
  • Patch immediately: Deploy the latest security‑only releases listed above. The patches are the only reliable mitigation.
  • Restrict credentials: Enforce multi‑factor authentication (MFA) for all SD‑WAN Manager accounts and apply the principle of least privilege. Disable or remove any low‑privileged accounts that do not require file‑upload capability.
  • Network segmentation: Isolate the management plane from the data plane and from the internet. Only allow trusted administrative workstations to reach the manager UI.
  • Log monitoring: Enable and regularly review vmanage-server.log, vmanage-appserver.log, and serviceproxy-access.log for path‑traversal patterns (e.g., ../../.. sequences) or unexpected WAR deployments.
  • Alerting: Create SIEM rules that trigger on HTTP POST requests to /api/v1/file-upload with suspicious filenames or on the creation of files under standalone/deployments/.
  • Threat intel: Track live exploitation signals on the VulnSocial CVE page for emerging attack tools or IoCs.

Remediation & Mitigation

  1. Identify all vulnerable deployments using inventory tools or manual checks.
  2. Apply the Cisco patch for your specific version (see Cisco advisory).
  3. If a patch cannot be applied immediately, disable the file‑upload API (e.g., block /api/v1/file-upload at the web‑application firewall).
  4. Enforce MFA and strong password policies for all SD‑WAN Manager accounts.
  5. Audit and remove unnecessary low‑privilege accounts that have write access.
  6. Monitor the manager logs for the indicators described above; set up automated alerts.
  7. Validate that the patch is effective by attempting a controlled file‑upload test with a benign payload.

Bottom Line

CVE-2026-20262 is a Medium severity, actively exploited file‑write flaw in Cisco Catalyst SD‑WAN Manager that can lead to root compromise. The risk is amplified by its presence in the CISA KEV catalog. Immediate deployment of Cisco’s security patches, combined with credential hardening and vigilant log monitoring, is essential to protect your SD‑WAN infrastructure.

References