NETWORK INCIDENTS

Exploited now

Remediation guide
Cisco · Catalyst SD-WAN Manager

CVE-2026-76504

Cisco Catalyst SD-WAN Manager API Authentication Bypass Vulnerability

CISA KEV
Known exploitedadded 30 Sep 2026; US federal deadline 3 Oct 2026
Exploit likelihood
39%99th percentile · FIRST EPSS, 2026-11-15
Severity
9.8 CriticalCVSS 3.1, Cisco
Last verified
30 Oct 2026against the sources below

1In plain language

A flaw in the API authentication of Cisco Catalyst SD-WAN Manager lets an attacker on the network, without logging in, bypass authentication and use the API as the admin user.

It affects SD-WAN Manager regardless of how it's configured.

Cisco became aware of active exploitation in September 2026, and CISA lists it as known to be exploited.

2Am I affected?

Every Cisco Catalyst SD-WAN Manager running an affected release is affected, regardless of system configuration. Cisco adds that systems exposed to the internet, with ports exposed to the internet, are at risk of exposure to compromise.

Not being reachable from the internet doesn't make a system unaffected. our analysis

Cisco's fix tables list release trains with the first release that includes the fix.

Affected releases are summarised by release train in the Fix table.

Check your version

A command to show the running SD-WAN Manager release: Not stated by vendor.

Cisco SD-WAN Cloud (Cisco managed) customers can check the current remediation status or software version with the Help function in the service GUI.

3Fix

Upgrade to a first fixed release in Cisco's table. Releases earlier than 20.9 must migrate to a fixed release.

Cisco's record also lists releases in the 20.10, 20.11, 20.13, 20.14 and 20.16 trains as affected, and the table has no row for them.

If you run one of those, move to a fixed release in one of the listed trains, planning the path with Cisco's upgrade matrix (below). our analysis

Cisco's record also lists 20.12.401 as affected, although it's numbered above the 20.12 first fixed release. Check your exact build with Cisco rather than comparing version numbers.

Cisco SD-WAN Cloud (Cisco managed) is fixed in release 20.15.605, and no user action is required.

To plan the upgrade, Cisco points to the Catalyst SD-WAN Upgrade Matrix. Source ↗

ProductReleaseFirst fixed release
Cisco Catalyst SD-WAN SoftwareEarlier than 20.9Migrate to a fixed release.
20.920.9.10.1
20.10Not stated by vendor: affected per the vendor's record; this train is not in the vendor's fix table
20.11Not stated by vendor: affected per the vendor's record; this train is not in the vendor's fix table
20.1220.12.8.220.12.401 is also listed as affected: check your exact build with Cisco. our analysis
20.13Not stated by vendor: affected per the vendor's record; this train is not in the vendor's fix table
20.14Not stated by vendor: affected per the vendor's record; this train is not in the vendor's fix table
20.1520.15.6.1
20.16Not stated by vendor: affected per the vendor's record; this train is not in the vendor's fix table
20.1820.18.4.1
26.126.1.2.1
26.226.2.1

4Can't patch tonight?

There are no workarounds. As a mitigation for on-prem deployments, restrict access from unsecured networks such as the internet. If internet access is required, allow only known, trusted hosts on the ports and protocols in the user guides, and put the SD-WAN Control Components behind a filtering device such as a firewall that lets only known, trusted hosts send traffic to them. In Cisco's cloud-hosted environments this mitigation is already deployed. Source ↗

Before deploying it, Cisco says:

  • Evaluate it for your own environment before deploying it: any workaround or mitigation may negatively impact your network's functionality or performance.

Cisco considers workarounds and mitigations temporary solutions until you can upgrade.

Cisco has also released a Live Protect shield for this CVE, as temporary partial protection while you plan the upgrade. It's not a fix: the only remediation is upgrading. With the shield applied, a legitimate user with URI encoding might not be able to log in to SD-WAN Manager. Source ↗

5Was I hit?

Cisco encourages auditing two logs for entries related to j_security_check from unknown or unauthorized IP addresses: /var/log/nms/containers/service-proxy/serviceproxy-access.log, and /var/log/nms/vmanage-server.log, in particular where it's called for users whose names start with viptela-reserved-. Those are documented system service accounts.

Cisco's example entries don't contain the literal text j_security_check, so a plain text search for it can miss them. Compare with Cisco's examples in the advisory. our analysis Link ↗

These indicators can also show up in normal operations, so assess them against your normal network posture to avoid false positives. Cisco's advisory shows example log lines. Source ↗

For help, open a Cisco TAC case as Severity 3 with CVE-2026-76504 in the title. Cisco encourages running request admin-tech on SD-WAN Manager (vManage) first, so the admin-tech file can go to TAC.

> request admin-tech

CISA's catalog flags this CVE for forensic triage, and its required action points to CISA's BOD 26-04 guidance and its Forensics Triage Requirements. Source ↗

6Sources

Summary of public vendor guidance. Verify against the vendor advisory before acting.

See CVE-2026-76504 in the exploited-now list (exploit likelihood, CISA's description, deadline).

More Cisco guides