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.
Security readout for executives and security teams
Plain-English summary
Cisco Catalyst SD-WAN Manager has an authenticated file-write flaw in its web UI. A low-privileged user could create or overwrite operating system files, potentially enabling later root escalation. Because CISA lists this CVE in KEV, treat it as actively exploited and prioritize exposed management systems.
Executive priority
Prioritize within emergency vulnerability management queues for any reachable SD-WAN Manager. Although the CVSS score is medium, active exploitation and potential root escalation on a network management platform create elevated business risk.
Technical view
The issue is improper validation of user input during file upload, mapped to CWE-22. An authenticated remote attacker can send a crafted HTTP request to an affected API endpoint and write arbitrary files on the underlying OS. CVSS is 6.5, but KEV status raises operational urgency.
Likely exposure
Organizations running Cisco Catalyst SD-WAN Manager, formerly SD-WAN vManage, on affected versions are exposed if attackers can authenticate to the web UI. Risk is highest where management access is broadly reachable or low-privileged accounts are weakly controlled.
Exploitation context
CISA KEV status supports active exploitation. The source states exploitation requires valid credentials with at least a lower-privileged, single-task user account. No user interaction is required, and successful exploitation affects file integrity, with possible later root escalation.
Researcher notes
Sources do not provide exploit details or fixed-version mappings in the supplied bundle. Validation should focus on version confirmation, account exposure, management-plane reachability, and evidence of unauthorized file writes. Avoid assuming unauthenticated exposure; credentials are required per Cisco’s description.
Mitigation direction
Review Cisco’s advisory for fixed releases and upgrade guidance.
Limit SD-WAN Manager web UI access to trusted management networks.
Audit and restrict low-privileged and single-task user accounts.
Enforce strong authentication and remove unused accounts.
Monitor for unexpected file creation or overwrites on managers.
Validation and detection
Inventory Cisco Catalyst SD-WAN Manager versions against Cisco’s affected list.
Confirm whether CISA KEV lists CVE-2026-20262 for your program scope.
Review web UI and API logs for suspicious authenticated file upload activity.
Check filesystem integrity for unexpected new or modified files.
Verify remediation against Cisco’s official advisory after changes.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-22 · source CWE mapping
Improper Limitation of a Pathname to a Restricted Directory
Improper Limitation of a Pathname to a Restricted Directory represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.