Skip to main content
All incident reports
Incident report

Cisco patches exploited Catalyst SD-WAN Manager zero-day (CVE-2026-76504)

Cisco has released fixes for a critical authentication bypass in Catalyst SD-WAN Manager, tracked as CVE-2026-76504, which lets an attacker with no credentials reach the management API as an administrator. Cisco says the flaw was actively exploited before it published an advisory on 30 September.

· First published

The short version

  • The flaw. CVE-2026-76504 carries a CVSS score of 9.8 and sits in the Manager's API session-based authentication. Cisco says the software mishandles URI encoding in an HTTP request, so a crafted request bypasses an authentication rule meant to restrict access to one API endpoint.
  • Exploitation. Cisco's Product Security Incident Response Team learned in September 2026 that the flaw was being exploited. The company has not said how many customers were attacked, when the attacks started, who carried them out, or what they did with the access.
  • Who is exposed. All Catalyst SD-WAN Manager deployments are affected regardless of configuration, and Cisco lists no other affected product. Managers reachable from the internet are at risk of compromise, according to Cisco.
  • The fix. Cisco has published first fixed releases for each supported release train and says there is no workaround. Cisco-managed SD-WAN Cloud is already patched; on-premises customers are told to restrict access to the Manager until they upgrade.

Timeline

DateEvent
FebruaryCisco patches CVE-2026-20127, an SD-WAN Manager information disclosure flaw that had been exploited since at least 2023.
MayCisco marks CVE-2026-20182, an authentication bypass in Catalyst SD-WAN Controller, as exploited in zero-day attacks to gain admin privileges.
JuneCisco warns of two more SD-WAN zero-days, CVE-2026-20245 and CVE-2026-20262, used to gain root privileges.
SeptemberCisco's PSIRT becomes aware that CVE-2026-76504 is being actively exploited; the flaw was found while the Technical Assistance Center handled a support case.
30 SepCisco publishes its advisory and the first fixed releases for CVE-2026-76504.
30 SepCISA adds CVE-2026-76504 to its Known Exploited Vulnerabilities catalogue.

How the bypass works

CVE-2026-76504 sits in the part of the Catalyst SD-WAN Manager API that handles session-based logins. Cisco says the Manager mishandles URI encoding in an HTTP request, so a crafted request slips past an authentication rule intended to protect a single API endpoint. The attacker needs no credentials, only the ability to send that request to the API. A successful request reaches the API as the admin user, which by default holds the netadmin role and can perform every operation on the device.

The flaw affects every deployment regardless of how it is configured, and Cisco lists no other product as affected. Managers reachable from the internet are at risk of compromise, the company says. According to The Hacker News, Cisco's support team came across the vulnerability while handling a customer case.

Exploitation and detection

Cisco's advisory, issued on 30 September, says its PSIRT became aware of active exploitation in September 2026. It does not say how many customers were attacked, when the attacks began, who was behind them, or what the attackers did with the administrative access. SecurityWeek reports that neither Cisco nor CISA has given details of the in-the-wild activity.

Cisco's indicators centre on j_security_check, the request path used for session logins. In its example one character is URI-encoded, giving /%6a_security_check, where %6a stands for the letter j; any character could be encoded, so that string is only an example. Analysts are pointed to serviceproxy-access.log under /var/log/nms/containers/service-proxy and to vmanage-server.log under /var/log/nms, looking for such requests from unknown IP addresses and for logins by accounts whose names begin with viptela-reserved-. Those entries also occur in normal operation, so each match has to be checked against expected activity.

The advisory includes no detection rule and does not say whether upgrading removes an attacker who already holds access. Cisco's advisories for the May flaw and the first June flaw said an update alone would not resolve a confirmed compromise and told customers to collect an admin-tech file before upgrading. For this vulnerability, Cisco asks customers to run request admin-tech first and open a Severity 3 TAC case with the CVE number in the title.

Patch status and wider context

Fixed releases exist for the 20.9, 20.12, 20.15, 20.18, 26.1 and 26.2 trains; deployments earlier than 20.9 are told to migrate to a fixed release. Cisco-managed SD-WAN Cloud is already fixed and those customers need take no action, according to Cisco. The Hacker News notes that the advisory omits several release trains that Cisco's May advisory covered, and does not name the Cloud-Pro or FedRAMP deployment types that the May and June advisories named. It also points out that the fixes for the May and June flaws are older, so a Manager updated for those still needs this patch.

BleepingComputer describes CVE-2026-76504 as the fifth SD-WAN zero-day exploited in 2026. CISA added it to the Known Exploited Vulnerabilities catalogue on the day Cisco disclosed it; the catalogue listed eight Cisco SD-WAN flaws added during 2026, and CISA has tagged 90 Cisco vulnerabilities since November 2021, including four in Catalyst SD-WAN Manager. Until an on-premises Manager is upgraded, Cisco advises allowing only known, trusted hosts and placing control components behind a firewall.

What is not known yet

  • Who carried out the attacks exploiting CVE-2026-76504.
  • How many customers or systems were compromised.
  • When exploitation of this flaw began.
  • What the attackers did with the administrative access, and whether they are still present.
  • Whether upgrading alone removes an attacker who already has access.
  • Whether the Cloud-Pro and FedRAMP deployment types named in earlier advisories are affected.

What to do

If you run Catalyst SD-WAN Manager

  1. Upgrade to the first fixed release for your release train; Cisco's advisory lists them and states there is no workaround.
  2. Until the upgrade is done, restrict access to the Manager from untrusted networks such as the internet, allow only known hosts, and keep control components behind a firewall.
  3. Search serviceproxy-access.log and vmanage-server.log for j_security_check requests, including encoded forms such as /%6a_security_check, from unknown IP addresses, and for logins by viptela-reserved- accounts.
  4. If you suspect compromise, collect an admin-tech file from the device and open a Severity 3 Cisco TAC case with CVE-2026-76504 in the title.

If you expose network management software

  1. Keep administrative interfaces such as HTTPS 443, SSH 22 and NETCONF 830 off the public internet; reach them through a jump host or a management subnet, as Cisco's hardening guide recommends.
  2. Review firewall rules that permit inbound access to network controllers or their APIs, and remove any that are not strictly required.

For everyone else

  1. Inventory management appliances that can push configuration to large parts of your network, and treat each one as a high-value target that must not be reachable from the internet.

Update log

  • First published.

Sources

New incident reports by email

One email a week with the reports published since the last one.

Want us to look at your domain?

Give us one apex domain and we'll send back a written snapshot of what is already visible from outside. No call required.