Blog / Security Advisories

Cisco SD-WAN and ISE API Authentication Bypasses (2026): Patch, Detect, and Protect Your Own APIs

In September 2026 Cisco disclosed two actively exploited flaws that let unauthenticated attackers into the APIs of Catalyst SD-WAN Manager and Identity Services Engine. Both are on CISA’s Known Exploited Vulnerabilities list. Here are the fixed versions, how to check for compromise, and why the same design mistake keeps showing up in web frameworks and reverse proxies.

· 10 min read

CVE-2026-76504 (Cisco Catalyst SD-WAN Manager, CVSS 9.8) and CVE-2026-76460 (Cisco ISE and ISE-PIC, CVSS 10.0) are API authentication bypasses that attackers used before patches were available. Neither has a workaround. The SD-WAN flaw is a textbook path interpretation conflict: the authentication check and the router disagreed about which URL was being requested. If your own APIs enforce login with path-matching rules in middleware or a proxy, the lesson applies to you too.

This article was created with AI assistance. Facts were checked against Cisco’s advisories as reported by security researchers and the published GitHub and GitLab advisories for the framework CVEs on October 28, 2026. Confirm details in the official advisories before acting.

TL;DR: what to install

If you runUpgrade toNotes
SD-WAN Manager 20.920.9.10.1CVE-2026-76504
SD-WAN Manager 20.1220.12.8.2CVE-2026-76504
SD-WAN Manager 20.1520.15.6.1CVE-2026-76504
SD-WAN Manager 20.1820.18.4.1CVE-2026-76504
SD-WAN Manager 26.126.1.2.1CVE-2026-76504
SD-WAN Manager 26.226.2.1CVE-2026-76504
SD-WAN Manager older than 20.9Migrate to a fixed releaseNo fix available
Cisco-managed SD-WAN cloudNo actionPatched by Cisco
ISE / ISE-PIC 3.1 to 3.53.1 P12, 3.2 P11, 3.3 P12, 3.4 P7, or 3.5 P4CVE-2026-76460

Federal agencies had until October 3, 2026 to remediate the SD-WAN flaw under CISA’s KEV directive, a three-day window. If you have not upgraded yet, treat both as emergency changes and assume the systems may already be compromised: work through the detection steps before you patch, because upgrading can rotate the logs you need.

Timeline

Date (2026)Event
February to JuneEarlier SD-WAN Manager bypass and privilege escalation CVEs, including CVE-2026-20127 and CVE-2026-20182 (both CVSS 10.0), are exploited
September 17Cisco discloses ISE CVE-2026-76460, CVSS 10.0, with exploitation confirmed
September 30Cisco discloses SD-WAN Manager CVE-2026-76504, CVSS 9.8, found during a support case involving in-the-wild exploitation. CISA adds it to KEV the same day
October 3CISA remediation deadline for federal agencies

SD-WAN Manager has been a repeated target all year. Researchers at Safeguard count CVE-2026-76504 as the ninth Cisco SD-WAN CVE added to the KEV catalog in 2026. Earlier campaigns attributed to the actor tracked as UAT-8616 included SSH key injection, NETCONF changes, version downgrades to reintroduce old bugs, and log clearing.

What went wrong: two layers, two views of one URL

Cisco describes CVE-2026-76504 as “improper handling of URI encoding in an HTTP request, which allows the request to bypass an authentication rule.” Its weakness class is CWE-177, improper handling of URL encoding. Research write-ups explain the mechanism:

  1. An authentication filter protected a sensitive login-check endpoint by comparing the raw request path against a literal string.
  2. The component that routed the request to its handler decoded the path first.
  3. A request whose path was percent-encoded differently did not match the filter’s string, so no check ran, yet it still reached the same handler.

The result was API access with the privileges of the built-in admin user. Because SD-WAN Manager is the control plane for every edge router in the fabric, that means control over routing, segmentation, and security policy across the whole network.

Cisco has said less about CVE-2026-76460 in ISE: an API endpoint did not enforce sufficient authentication, letting a crafted request bypass the management interface. The outcome is the same: an unauthenticated attacker reaching functions that should require an administrator.

The general pattern is called an interpretation conflict (CWE-436). Whenever one component decides whether a request is allowed and another decides where it goes, any difference in how they read the path is a potential bypass. Typical differences are percent-decoding, case, duplicate slashes, dot segments, path parameters after a semicolon, and trailing slashes.

The same bug class in 2026 web frameworks and proxies

This is not a Cisco-only problem. Several widely used open-source projects fixed the same kind of flaw this year. If you use any of them, check your versions:

ProjectCVECVSSLayers that disagreedFixed in
@fastify/expressCVE-2026-338089.1Fastify normalized the URL for routing, but Express middleware received the original URL4.0.5
Traefik StripPrefixCVE-2026-4802010.0Route matching happened before prefix stripping and normalization, so a public route could resolve to a protected backend path3.6.19, 3.7.3
@fastify/middieCVE-2026-141989.1Middleware decoded encoded slashes before matching while the router kept them encoded9.3.3
Nuxt route rulesCVE-2026-1141316.5Route rules compared encoded paths while the page router matched decoded ones, so rule-attached middleware was skipped3.21.4, 4.4.4

Traefik also fixed a related ReplacePathRegex issue, CVE-2026-65600. The Nuxt fix shipped on October 23, 2026, so many projects have not picked it up yet. Run npm ls nuxt @fastify/express @fastify/middie or check your proxy image tags, and upgrade.

Check Cisco systems for compromise

Do this before patching. Researchers who analyzed CVE-2026-76504 recommend:

  1. Preserve evidence. Run request admin-tech on SD-WAN Manager and export logs off the box.
  2. Review the service proxy access log (/var/log/nms/containers/service-proxy/serviceproxy-access.log) for requests to the login-check endpoint whose raw path contains percent-encoded letters. Legitimate clients do not encode ordinary letters and digits, as RFC 3986 advises against it, so any such request deserves investigation.
  3. Review the server log (/var/log/nms/vmanage-server.log) for activity by usernames beginning with viptela-reserved-.
  4. Trace follow-on API calls from unfamiliar source IPs and compare accounts, SSH keys, templates, and policies against a known-good baseline.
  5. Check external logs too. For ISE, Cisco warns attackers may delete local logs, so cross-check firewall and network logs.

Cisco Talos published Snort coverage (SID 67179) for the SD-WAN flaw. If you find signs of compromise, follow your incident response process and rotate every admin credential and key after upgrading.

Interim mitigations

  • Restrict management access. Limit SD-WAN Manager (TCP 443, 22, and 830) and the ISE admin interface to trusted management hosts. A management plane should never be reachable from the internet.
  • Cisco Live Protect. Cisco offers a temporary shield for SD-WAN Manager. Reports note it may block some legitimate logins, so test before relying on it.
  • Plan the upgrade anyway. Cisco states there is no workaround for either CVE. Mitigations reduce exposure; only the fixed releases close the hole.

How to keep this bug class out of your own APIs

Most teams do not build network appliances, but almost every team has an API behind a proxy and a framework with middleware. These rules remove the conditions that make interpretation conflicts exploitable:

  • Make authentication deny by default. Require a valid session on every route, then explicitly mark the few public ones. A missed match then fails closed, not open.
  • Attach checks to routes, not path strings. Use your framework’s route-level guards, decorators, or handler hooks, which run after routing and see the same route the handler does. Avoid allowlists and denylists written as string prefixes or regular expressions over the raw URL.
  • Normalize once, at the edge. Decide on a single canonical form at your gateway or proxy, and reject requests whose path is ambiguous instead of trying to clean them up.
  • Align settings across layers. Options such as duplicate-slash handling, semicolon delimiters, trailing-slash matching, and case sensitivity must agree between proxy, router, and middleware. CVE-2026-33808 was triggered by enabling normalization in one layer but not the next.
  • Authorize at the object, too. Even a perfect login check does not stop a signed-in user from reaching another user’s data. Pair authentication with object and function level authorization; see BFLA vs BOLA.
  • Keep the edge patched. Proxies, API gateways, and middleware packages are part of your authentication path. Track their advisories like you track your runtime’s; see our nginx 2026 guide for an example.

Verify authentication on every endpoint

Code review finds string-matching auth rules, but only a running system shows how your proxy, router, and middleware behave together. Build verification into your release process:

  1. Start from a complete inventory. Generate the endpoint list from your OpenAPI spec or Postman collection, and compare it with your gateway routes to catch undocumented endpoints. Our guide to writing a testable OpenAPI spec covers marking which operations are public.
  2. Call each non-public endpoint without credentials against a staging environment that uses the same proxy configuration as production, and confirm it returns 401 or 403, never data.
  3. Repeat with each role to confirm lower-privileged users cannot reach admin functions.
  4. Add framework-level tests that assert every registered route has an authentication guard unless it is on the public list. This catches new routes that someone forgot to protect.
  5. Run it continuously. Put the checks in your CI/CD pipeline and rerun them after every proxy, gateway, or framework upgrade, since a change in normalization defaults can open a gap without any application code change.

How DAST tools help you catch issues like this sooner

No scanner can patch a Cisco appliance, and upgrading is the only fix for these two CVEs. What the incidents show is that authentication bugs live in the interaction between components, which is exactly what dynamic application security testing observes: it tests the deployed system from outside, through the same proxy and framework attackers hit.

DastPilot scans your APIs from an OpenAPI spec or Postman collection, as every role you configure. Checks most relevant to authentication bypasses:

  • Missing authentication: calls every documented endpoint with no credentials and flags any that respond with data.
  • Token handling: tests tampered, expired, and malformed JWTs; see JWT authentication vulnerabilities.
  • Privilege escalation (BFLA): replays admin operations as lower-privileged roles.
  • Object-level authorization (BOLA): swaps identifiers between users to find cross-account access.
  • Exposed internals: flags unauthenticated debug endpoints, public API schemas, and version-revealing headers that help attackers pick targets.
  • Regression tracking: each scan is compared with the last, so an endpoint that loses its auth guard after a proxy or framework upgrade is flagged as reopened.

DAST complements patching, code review, and dependency scanning. Use dependency scanning to find the vulnerable framework versions listed above, and DAST to confirm that what is deployed refuses unauthenticated requests. For a full checklist, see our API penetration testing checklist and the OWASP API Security Top 10 guide.

Frequently asked questions

What is CVE-2026-76504?

CVE-2026-76504 is a CVSS 9.8 authentication bypass in the API of Cisco Catalyst SD-WAN Manager, formerly vManage. The authentication rule protecting a login endpoint compared the raw request path, while routing used the decoded path, so a request with percent-encoded characters reached the endpoint without being checked. Attackers gain admin access to the Manager API. Cisco published the advisory on September 30, 2026 and confirmed active exploitation.

Which Cisco SD-WAN Manager versions fix CVE-2026-76504?

The first fixed releases are 20.9.10.1, 20.12.8.2, 20.15.6.1, 20.18.4.1, 26.1.2.1, and 26.2.1. Releases older than 20.9 have no fix and must migrate to a fixed train. The Cisco-managed cloud was patched by Cisco. There is no workaround.

Which Cisco ISE versions fix CVE-2026-76460?

Cisco ISE and ISE-PIC 3.1 Patch 12, 3.2 Patch 11, 3.3 Patch 12, 3.4 Patch 7, and 3.5 Patch 4 fix CVE-2026-76460, a CVSS 10.0 authentication bypass in an ISE API endpoint. Cisco has confirmed exploitation and says there are no workarounds.

Can this kind of authentication bypass affect my own web application?

Yes. In 2026 the same class of bug, where two layers interpret a request path differently, was fixed in @fastify/middie (CVE-2026-14198), @fastify/express (CVE-2026-33808), Traefik StripPrefix (CVE-2026-48020), and Nuxt route rules (CVE-2026-114131). Applications that enforce authentication with path-matching middleware or proxy rules are most at risk.

How do I prevent path normalization authentication bypasses?

Make authentication deny by default and attach it to routes or handlers instead of matching path strings. Normalize the path once, at the edge, and reject ambiguous requests. Keep proxy and application normalization settings consistent, and keep middleware and proxy dependencies patched.

Can a DAST scanner find authentication bypass vulnerabilities?

A DAST scanner cannot tell you whether a Cisco appliance is patched. DAST tools such as DastPilot call every documented API endpoint without credentials and with each configured role, and flag endpoints that return data when they should refuse, which catches missing and inconsistent authentication in your own APIs before attackers do.

Prove every endpoint refuses unauthenticated requests

DastPilot tests every documented API endpoint without credentials and as each role, flags missing authentication, BOLA, and BFLA, and rechecks them on every scan. 30-day free trial, no credit card required.