Attackers are actively exploiting a Cisco SD-WAN zero-day that can give them administrator access without a password. The flaw, tracked as CVE-2026-76504, sits in Cisco Catalyst SD-WAN Manager, the platform formerly known as vManage. It carries a CVSS score of 9.8.

For Canadian organizations that run branch networks on Cisco SD-WAN, this is not a “patch next month” issue. In this article, we explain how the Cisco SD-WAN zero-day works, which releases fix it, and what your team should check today.

What Happened With the Cisco SD-WAN Zero-Day

Cisco published an urgent advisory after it found exploitation while working on a Technical Assistance Center (TAC) support case. Shortly after, the U.S. Cybersecurity and Infrastructure Security Agency (CISA) added the flaw to its Known Exploited Vulnerabilities catalog on September 30. CISA gave U.S. federal civilian agencies until October 3 to fix it.

That deadline was very short. In other words, the risk is real and immediate. Although CISA’s order applies to U.S. agencies, Canadian companies face the same attackers and the same exposed devices.

How the Authentication Bypass Works

Glowing circuit paths converging on a chip core, illustrating the Cisco SD-WAN zero-day authentication bypass

The bug lives in how SD-WAN Manager handles URI encoding during API session-based authentication. According to the Cisco security advisory, a crafted HTTP request can slip past an authentication rule that should protect a specific API endpoint.

As a result, an unauthenticated remote attacker can reach the API with admin privileges. Cisco’s indicators show attackers replacing a character with its URL encoding. For example, they send “%6a” instead of the letter “j” when calling the j_security_check endpoint.

Cisco stresses that this is only one example. Any single encoded character in the request can be used. The flaw affects SD-WAN Manager regardless of configuration, and Cisco lists no workaround.

Why SD-WAN Manager Is a High-Value Target

SD-WAN Manager is the brain of the network. It pushes policies, routes and configurations to every edge router across your sites. Therefore, an attacker with admin access to it can see and change a great deal.

Cisco has not said what attackers did after they got in. Even so, possible outcomes include exposed network configurations, unauthorized policy changes, and a foothold for deeper attacks. Moreover, systems with management ports open to the internet face the highest risk.

This also fits a pattern. Edge and management appliances have been hit hard in recent weeks. For instance, we recently covered the FortiMail zero-day CVE-2026-104286, which also targeted an internet-facing appliance.

Fixed Releases for the Cisco SD-WAN Zero-Day

The only real fix is to upgrade. Fixed releases for SD-WAN Manager, by branch, are:

  • 20.9.10.1
  • 20.12.8.2
  • 20.15.6.1
  • 20.18.4.1
  • 26.1.2.1
  • 26.2.1

If you use Cisco SD-WAN Cloud (Cisco Managed), release 20.15.605 already addresses the flaw. No customer action is needed there.

In addition, Cisco released a Live Protect shield for CVE-2026-76504. It offers temporary, partial protection while you plan the upgrade. However, Cisco warns that legitimate users who log in with URI encoding may be blocked while the shield is active. So treat it as a short bridge, not a fix.

How to Check for Signs of Compromise

Cyan and green data streams flowing across a dark background, symbolizing log review after the Cisco SD-WAN zero-day

Patching closes the door. It does not tell you whether someone already walked through it. That is why Cisco and analysts at eSecurity Planet recommend a compromise assessment alongside the upgrade.

Start with two log files on each on-premises SD-WAN Manager:

  • /var/log/nms/containers/service-proxy/serviceproxy-access.log: look for requests to an encoded j_security_check path from unknown or unauthorized IP addresses.
  • /var/log/nms/vmanage-server.log: look for j_security_check entries for user names that start with “viptela-reserved-“.

Keep in mind that some of these entries can appear during normal operations. Consequently, compare them with your known admin IP addresses before you raise an alarm.

If anything looks suspicious, generate an admin-tech archive with the request admin-tech command. Then open a Severity 3 case with Cisco TAC and put CVE-2026-76504 in the title.

A Practical Response Plan for Canadian Teams

Here is a short plan you can follow this week:

  1. Inventory every SD-WAN Manager instance, including lab and backup systems.
  2. Upgrade each one to the fixed release for its branch.
  3. Remove management interfaces from the public internet. Place them behind a firewall or a dedicated admin network.
  4. Review the two log files above for the full period your system was exposed.
  5. Rotate admin credentials and API tokens after the upgrade.
  6. Document what you did, since it may matter for privacy and incident reporting duties.

For many small and mid-sized organizations, the hardest step is visibility. You cannot patch a controller that nobody remembers deploying. Asset inventory, therefore, is your first line of defence.

The Bottom Line

The Cisco SD-WAN zero-day is serious because it targets the control point of the whole network. Exploitation is confirmed, the CVSS score is 9.8, and there is no workaround. Upgrade now, lock down management access, and check your logs.

If your team needs help assessing Cisco SD-WAN exposure, planning upgrades, or reviewing logs, Karavi can help. Reach out, and we will help you close the gap quickly and safely.

No comment

Leave a Reply

Your email address will not be published. Required fields are marked *