Cisco Catalyst SD-WAN Manager CVE-2026-76504: One Encoded Character Bypasses Admin Auth
An unauthenticated attacker can take over Cisco Catalyst SD-WAN Manager by percent-encoding one character in a request. CVSS 9.8, actively exploited, no workaround, KEV deadline 3 October.
What Happened
On 30 September 2026, Cisco published advisory cisco-sa-sdwan-webauth-xr8beuuU for CVE-2026-76504, a critical authentication bypass in Catalyst SD-WAN Manager, the on-premises console formerly sold as SD-WAN vManage. The flaw carries a CVSS 3.1 base score of 9.8 and lets an unauthenticated, remote attacker reach the Manager's API with the privileges of the admin user. Cisco tracked the issue internally as bug CSCww79570 and classified it as CWE-177, improper handling of URL (hex) encoding. CISA named it the "Cisco Catalyst SD-WAN Manager Hex Encoding Vulnerability" when it added the CVE to the Known Exploited Vulnerabilities catalog the same day, setting a remediation deadline of 3 October 2026 for federal civilian agencies.
Cisco's Product Security Incident Response Team said it became aware of active exploitation in September 2026, and that the vulnerability was found while the Technical Assistance Center was working a support case. The advisory does not say how many customers were hit, when the attacks began, who ran them, or what the attackers did with the access. There is no workaround. Fixed software is the only remediation, and the exposure applies to the Manager regardless of how it is configured.
How the Bypass Works
The weakness lives in the API's session-based authentication management. Catalyst SD-WAN Manager enforces an authentication rule that is meant to restrict access to a specific API endpoint. Because the Manager mishandles URI encoding, a request that percent-encodes a single character slips past that rule while still being routed to the protected handler behind it. Cisco's own indicator-of-compromise example shows a POST to /%6a_security_check, where %6a is the hex encoding of the letter j, standing in for the real login path j_security_check. Any single character in the request can be encoded; %6a is only an illustration.
The result is a classic parser disagreement: the component that decides whether to apply the auth rule and the component that finally services the request do not agree on what the URL says. The attacker needs no credentials and no user interaction, and the admin account that gets handed over holds the netadmin role, which can perform every operation on the Manager and the fabric it controls. The NVD CVSS vector is AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, and CISA's SSVC decision marks exploitation as active, automatable as yes, and technical impact as total. The decode-mismatch mechanism at the heart of this bug is the subject of our explainer, How an Encoding Mismatch Between Two Parsers Defeats an Access Rule.
Who Is Affected
Every on-premises Catalyst SD-WAN Manager is affected unless it runs a fixed release. NVD lists affected builds as far back as the 17.2 and 18.x trains, and Cisco's fixed-software table spans the 20.9 through 26.2 release trains. The cloud-based Cisco SD-WAN Cloud (Cisco Managed) offering was fixed in release 20.15.605, and customers there need take no action. Managers with ports exposed to the internet are the ones at immediate risk, and Cisco has stated that the network-level mitigation it recommends is already deployed in its Cloud Hosted environments.
The blast radius is what makes this urgent. Catalyst SD-WAN Manager is a single pane that administers large SD-WAN estates, up to 6,000 devices in one deployment per BleepingComputer's reporting. Admin on the Manager is not admin on one box; it is control of the policy, routing, and configuration pushed to every edge device in the fabric.
Immediate Actions
Upgrade on an emergency basis, outside the normal patch cycle. The first fixed releases are: 20.9.10.1 for the 20.9 train, 20.12.8.2 for 20.12, 20.15.6.1 for 20.15, 20.18.4.1 for 20.18, 26.1.2.1 for 26.1, and 26.2.1 for 26.2. Anything earlier than 20.9 must migrate to a fixed release. Note that the fixed builds here are newer than the ones that resolved Cisco's May and June SD-WAN advisories, so a Manager last patched for those still needs this update.
Because there is no workaround, the only stopgap is to cut off reachability. Keep the Manager off unsecured networks, allow only known, trusted hosts, and put the control components behind a filtering device. Administrative interfaces should never face the internet directly; HTTPS to the Manager should arrive through a jump host or a management subnet. Working out what is actually exposed is a project in itself, which we cover in How to Find Which of Your Admin Consoles Are Reachable From the Internet.
Assume you may already have been hit and hunt for it. Cisco directs defenders to two logs: serviceproxy-access.log under /var/log/nms/containers/service-proxy/ and vmanage-server.log under /var/log/nms/. Look for j_security_check requests that contain an encoded character, and for the same path invoked for users whose names begin with viptela-reserved-, both from unknown or unauthorized IP addresses. These entries can also occur in normal operation, so measure them against your baseline. A detection signature ships as Snort rule 67179. Preserve evidence before you patch: Cisco's guidance for its recent SD-WAN flaws was that an update alone will not remove an attacker who already has access. Run request admin-tech to collect an admin-tech file, then open a Severity 3 TAC case with the CVE in the title. CISA's KEV entry flags forensic triage as required.
The Bigger Picture
CVE-2026-76504 is, by BleepingComputer's count, the fifth SD-WAN zero-day actively exploited in the wild this year; The Hacker News reports that the KEV catalog listed eight Cisco SD-WAN flaws added in 2026 as of 30 September. Whichever tally you use, the pattern is the same: internet-reachable network control planes keep yielding unauthenticated bypasses, and the fixes keep arriving only after exploitation. Rapid7 noted two earlier 2026 authentication bypasses in the Manager's peering stack, CVE-2026-20127 and CVE-2026-20182, both distinct from this API path.
The hardest part of this advisory is the phrase "no workarounds available." When a vendor cannot offer a mitigating configuration, the usual stall tactics evaporate and the decision collapses to patch now or disconnect. Why 'No Workaround Available' Should Change How You Triage a Patch walks through that calculus. For defenders, the durable lesson is that a management console reachable from the internet is a liability no matter how well it is hardened, because the next bypass is a decode mismatch you have not seen yet.
Sources
- https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-sdwan-webauth-xr8beuuU
- https://nvd.nist.gov/vuln/detail/CVE-2026-76504
- https://www.cisa.gov/news-events/alerts/2026/09/30/cisa-adds-one-known-exploited-vulnerability-catalog
- https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json
- https://www.rapid7.com/blog/post/etr-critical-cisco-catalyst-sd-wan-manager-api-authentication-bypass-exploited-in-the-wild-cve-2026-76504/
- https://www.bleepingcomputer.com/news/security/cisco-warns-of-new-sd-wan-authentication-bypass-zero-day-exploited-in-attacks/
- https://thehackernews.com/2026/09/cisco-warns-of-attackers-exploiting.html