dbcve.org
Catalyst Sd Wan ManagerApplication · Cisco

CVE-2020-26064

HIGH · 8.1 CVSS v3.1 Published 2023-08-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
A vulnerability in the web UI of Cisco SD-WAN vManage Software could allow an authenticated, remote attacker to gain read and write access to information that is stored on an affected system. The vulnerability is due to improper handling of XML External Entity (XXE) entries when parsing certain XML files. An attacker could exploit this vulnerability by persuading a user to import a crafted XML file with malicious entries. A successful exploit could allow the attacker to read and write files within the affected application.

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 confidence

An XXE (XML External Entity) injection vulnerability in Cisco SD-WAN vManage's web UI allows authenticated remote attackers to read and write arbitrary files on the affected system by importing specially crafted XML files containing malicious entity definitions.

MitigationApply the relevant Cisco security patch/updates for SD-WAN vManage. Until patched, restrict user privileges for XML file import functionality and monitor for suspicious file imports.

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
Affected:= 17.2.4= 17.2.5= 17.2.6= 17.2.7= 17.2.8= 17.2.9= 17.2.10= 18.2.0= 18.3.0= 18.3.1= 18.3.1.1= 18.3.3

CVSS 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
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Cisco SD-WAN vManage is installed
    Identify the installed product by checking system information, running 'show version' on the device, or accessing the vManage admin interface. Look for 'Cisco SD-WAN Manager' or 'vManage' in the system identification.
    Affected if The system is not running Cisco SD-WAN vManage software.
  2. Determine the installed vManage version
    Access the vManage web UI and navigate to Administration > Settings > Software Repository, or use the CLI command 'request software version' to display the current software version. Compare this version number to the affected list: 17.2.4, 17.2.5, 17.2.6, 17.2.7, 17.2.8, 17.2.9, 17.2.10, 18.2.0, 18.3.0, 18.3.1, 18.3.1.1, 18.3.3
    Affected if The installed version matches any of the listed affected versions.
  3. Verify the XML import feature is accessible
    Log into the vManage web UI and navigate to the Configuration > Templates or Configuration > Device area to locate any XML import, upload, or template import functionality. Check if the feature is present in the menu options available to your user account.
    Affected if The XML import feature exists and is accessible to your user account.
  4. Review user access to XML import functionality
    Navigate to Administration > User Management or Administration > Users in vManage. Review which users or user groups have permission to import XML files or access template import features. Identify if low-privilege or unauthorized users have this capability.
    Affected if Users without proper authorization can access or use the XML import feature.

The environment is affected if Cisco SD-WAN vManage is running and the installed version matches one of the affected versions (17.2.4 through 18.3.3) AND the XML import feature via the web UI is accessible to users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the relevant Cisco security patch/updates for SD-WAN vManage. Until patched, restrict user privileges for XML file import functionality and monitor for suspicious file imports.

Recommended fix Moderate confidence

Cisco SD-WAN vManage 17.2.8 or later (17.3.x/17.4.x recommended for longer support)

  1. 1. Identify the current SD-WAN vManage version by logging into the vManage web UI and navigating to Administration > Settings > Software Update, or use the CLI command 'request software show'
  2. 2. Schedule a maintenance window for the upgrade, ensuring you have a full backup of the vManage configuration
  3. 3. Download the fixed software release (17.2.8 or later) from Cisco's software download center at software.cisco.com
  4. 4. Upload the new software image to vManage via the web UI (Administration > Software Update > Upload Image) or via CLI
  5. 5. Initiate the upgrade through the web UI (Administration > Software Update > Install) or CLI, selecting the option to install the image on the same device
  6. 6. Wait for the installation to complete and for vManage services to restart - this may take 15-30 minutes
  7. 7. Verify the upgrade was successful by logging back into vManage and confirming the new version number in Administration > Settings > Software Update
  8. 8. Test that the XML import functionality works correctly with legitimate XML files to confirm normal operation
Caveat Standard minor version upgrades within 17.2.x are typically non-breaking; ensure valid configuration backup before upgrade; some feature behavior changes may occur between minor releases

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
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,152.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-26064 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-26064 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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