Cisco has fixed CVE-2026-76504, an authentication bypass in the API of Cisco Catalyst SD-WAN Manager. Cisco rates it Critical with a CVSS 3.1 base score of 9.8. Cisco says it became aware of active exploitation in September 2026, and CISA added the flaw to its KEV catalog on 2026-09-30.
Advisory details
- Title: Cisco Catalyst SD-WAN Manager API Authentication Bypass Vulnerability.
- Advisory ID: cisco-sa-sdwan-webauth-xr8beuuU, version 1.1 (Final).
- First published: 2026-09-30 13:00 GMT. Last updated: 2026-10-02 23:18 GMT.
- Severity: Critical, CVSS 3.1 base score 9.8.
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:X/RL:X/RC:X.
- Weakness: CWE-177. Cisco bug ID: CSCww79570.
- Workarounds: none available.
- Source: found during the resolution of a Cisco TAC support case.
- Detection: Snort rule 67179.
What the flaw does
The flaw sits in the API session-based authentication management of Catalyst SD-WAN Manager. It lets an unauthenticated, remote attacker reach the system with the privileges of the admin user.
The cause is improper handling of URI encoding in an HTTP request. A crafted request can bypass an authentication rule meant to restrict access to a specific API endpoint. A successful attack gives the attacker API access as the admin user.
Affected products
The flaw affects Cisco Catalyst SD-WAN Manager regardless of system configuration. Cisco lists no other products as affected.
Fixed releases
| Cisco Catalyst SD-WAN Software Release | First Fixed Release |
|---|---|
| Earlier than 20.9 | Migrate to a fixed release. |
| 20.9 | 20.9.10.1 |
| 20.12 | 20.12.8.2 |
| 20.15 | 20.15.6.1 |
| 20.18 | 20.18.4.1 |
| 26.1 | 26.1.2.1 |
| 26.2 | 26.2.1 |
Cisco also fixed the flaw in Cisco SD-WAN Cloud (Cisco Managed) Release 20.15.605. Cloud customers do not need to take action. They can check the remediation status or version through the Help function in the service GUI.
Live Protect shield and mitigation
Cisco released a Live Protect shield for this CVE. It gives temporary, partial protection while upgrades are planned. Upgrading to a fixed release is the only remediation. One side effect: a legitimate user with URI encoding might not be able to log in to SD-WAN Manager.
For on-premises deployments, Cisco advises restricting access from unsecured networks such as the internet. Where internet access is needed, allow only known, trusted hosts on documented ports and protocols. Cisco also advises placing the control components behind a firewall. For Cloud Hosted environments, Cisco says this mitigation is already deployed.
Indicators of compromise
Cisco says Catalyst SD-WAN Manager systems with ports exposed to the internet are at risk of compromise. Some indicators can appear during normal operations, so they must be compared with normal network posture.
- Check
/var/log/nms/containers/service-proxy/serviceproxy-access.logforj_security_checkentries from unknown or unauthorized IP addresses. Cisco's example showsPOST /%6a_security_check. - Check
/var/log/nms/vmanage-server.logforj_security_checkentries from unknown IP addresses, for users whose names start withviptela-reserved-. - The
%6avalue (the letter j) is only an example. Any single encoded character in the request can be used.
For help, Cisco asks customers to open a Severity 3 TAC case with the CVE ID in the title. They should first run request admin-tech on SD-WAN Manager and provide the file.
Exploitation status
Cisco states that in September 2026 its PSIRT became aware of active exploitation of this vulnerability. CISA lists it in the KEV catalog as "Cisco Catalyst SD-WAN Manager Hex Encoding Vulnerability". CISA added it on 2026-09-30 with a due date of 2026-10-03 for federal agencies. Known ransomware campaign use is "Unknown", and forensic triage is "Yes".
Terms explained
- Catalyst SD-WAN Manager: the central management system, also called vManage, for a Cisco SD-WAN network.
- URI encoding: writing a character as % plus its hex code, for example %6a for j.
- CWE-177: improper handling of URL encoding (hex encoding). The software does not decode such input correctly before checking it.
- AV:N, AC:L: the attack works over the network with low complexity.
- PR:N, UI:N: no login and no user action are needed.
- S:U: scope unchanged; the impact stays within the vulnerable component.
- C:H, I:H, A:H: high impact on confidentiality, integrity and availability.
- E:X, RL:X, RC:X: temporal metrics not defined; they do not change the score.
- KEV and BOD 26-04: CISA's catalog of flaws with evidence of real attacks, and the directive that sets remediation deadlines for US federal agencies.
What This Means for IT Teams
Every on-premises Catalyst SD-WAN Manager deployment is in scope, whatever its configuration. Cisco-managed SD-WAN Cloud is already fixed in 20.15.605 and needs no action.
Check the running release against the table and upgrade to the first fixed release for that train. Releases earlier than 20.9 must migrate to a fixed release. The Live Protect shield and access restrictions only reduce exposure until the upgrade is done.
The flaw is under attack and needs no credentials, so internet-reachable managers deserve attention first. Reviewing the two log files Cisco names is part of the response, not only patching. Keeping the management plane behind a firewall fits ongoing network management practice.
NVD cross-check
- Agrees: the description, CWE-177 and the CVSS 3.1 score of 9.8 with the same base vector, provided by Cisco ([email protected]).
- Score version: NVD lists no CVSS 4.0 score.
- Versions: NVD's CPE data marks versions before 20.9.10.1, and the 20.12, 20.15, 20.18 and 26.1 trains before their fixed builds, as vulnerable. This matches Cisco's table. NVD also lists release 26.2 (no update level) as vulnerable.
- Status: Analyzed, with the same KEV date added (2026-09-30).
Related coverage: Cisco ASA and FTD SSL VPN denial-of-service flaw CVE-2026-20349 (KEV).


