Skip to content
VulniPulse
Sign in
Advisory severityMedium6.5Cisco

Medium [CVE-2026-20294] Cisco Catalyst SD-WAN Manager Information Disclosure Vulnerability

This medium-severity Cisco advisory covers CVE-2026-20294 affecting Catalyst SD-WAN Manager.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

cisco-sa-sdwan-infodis-SPuJBDCe Source published Source updated

VulniPulse record published Record updated

CVE-2026-20294
Affected products & platforms
CiscoSD-WANCatalyst SD-WAN
Open source advisory

Android app · Google Play

Monitor future Cisco CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery
Get CVE alertsSee app features

Summary

A vulnerability in the web-based management interface of Cisco Catalyst SD-WAN Manager could allow an authenticated, remote attacker to view sensitive information in clear text on an affected system.

This vulnerability is due to insufficient access control enforcement for specific template types that are not included in the encryption allowlist. A low-privileged attacker could exploit this vulnerability by viewing logs on the local system or on a remote logging server.

A successful exploit could allow the attacker to view sensitive authentication credentials, which could lead to further compromise of network infrastructure and connected services.

Cisco has released software updates that address this vulnerability. There are no workarounds that address this vulnerability.

Affected versions
  • Scope: At the time of publication, this vulnerability affected Cisco Catalyst SD-WAN Manager, regardless of device configuration.
  • Earlier than 20.91 — Migrate to a fixed release
  • Release 20.9 (first fixed: 20.9.10)
  • Release 20.10 (first fixed: 20.12.8)
  • Release 20.111 (first fixed: 20.12.8)
  • Release 20.12 (first fixed: 20.12.8)
  • Release 20.131 (first fixed: 20.15.6)
  • Release 20.141 (first fixed: 20.15.6)
  • Release 20.15 (first fixed: 20.15.6)
  • Release 20.161 (first fixed: 20.18.4)
  • Release 20.18 (first fixed: 20.18.4)
  • Release 26.1 (first fixed: 26.1.2)
  • Release 26.2 (first fixed: 26.2.1)

Official advisory · high-confidence parse· fetched 24 days ago·verify at source

Fixed versions
  • 20.9.10
  • 20.12.8
  • 20.15.6
  • 20.18.4
  • 26.1.2
  • 26.2.1

Official advisory · high-confidence parse· fetched 24 days ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • Upgrade to the first fixed release for your train per the Fixed Releases table in this advisory.
  • Earlier than 20.91: migrate to a fixed release.
  • Release 20.9: upgrade to 20.9.10.
  • Release 20.10: upgrade to 20.12.8.
  • Release 20.111: upgrade to 20.12.8.
  • Release 20.12: upgrade to 20.12.8.
  • Release 20.131: upgrade to 20.15.6.
  • Release 20.141: upgrade to 20.15.6.
  • Release 20.15: upgrade to 20.15.6.
Workaround status
  • There are no workarounds that address this vulnerability.

Official advisory · high-confidence parse· fetched 24 days ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.