Cisco Patches Actively Exploited ASA and FTD Zero-Day CVE-2026-76418 — Crafted SSL VPN Requests Crash Firewalls Before You Ever Log In

Cisco Patches Actively Exploited ASA and FTD Zero-Day CVE-2026-76418 — Crafted SSL VPN Requests Crash Firewalls Before You Ever Log In

Cisco Patches Actively Exploited ASA and FTD Zero-Day CVE-2026-76418 — Crafted SSL VPN Requests Crash Firewalls Before You Ever Log In

Cisco has shipped fixes for a denial-of-service zero-day in Secure Firewall Adaptive Security Appliance (ASA) and Threat Defense (FTD) software that attackers are already exploiting in the wild. Tracked as CVE-2026-76418 and rated 8.6 (high), the flaw lives in the Remote Access SSL VPN service: an unauthenticated, remote attacker sends a crafted request while connecting to the SSL VPN and the affected device reloads unexpectedly. Cisco's Product Security Incident Response Team said it became aware of active exploitation in October 2026 but shared no details about who is behind the attacks or who is being hit — no indicators of compromise came with the advisory.

The bug is rooted in logic errors that appear when secondary authentication is configured on a tunnel group. Three conditions must line up for a firewall to be vulnerable: it runs an unpatched ASA or FTD release, its SSL remote access VPN login service is reachable, and a tunnel group in scope carries secondary authentication. One detail in the advisory deserves emphasis: "a successful VPN login is not required to reach the affected processing path" — the crash happens during connection handling, not after authentication. The vulnerability surfaced through a Cisco TAC support case (Eric Fernald is credited with the find), and Cisco's cloud-delivered firewall and management offerings, Secure Access, and the Secure Firewall Management Center are not affected.

Fixed releases now cover every supported train: ASA 9.16.4.104, 9.18.4.96, 9.20.4.50, 9.22.3.200, 9.23.1.48, and 9.24.1.27/9.24.10.1, and FTD 7.0.11, 7.2.13, 7.4.9, 7.6.7, 7.7.14, 10.0.3, and 10.1.1. There is no workaround. Administrators who cannot patch immediately can reduce exposure by disabling secondary authentication on the default DefaultWEBVPNGroup or on user-configured tunnel group lists — but Cisco explicitly cautions that dropping secondary authentication makes the remote access VPN less secure and recommends upgrading instead. The exposure base is not small: internet monitoring platform Shadowserver currently tracks more than 51,000 Cisco ASA SSL VPN devices exposed online, with no breakdown of how many are patched.

The pattern around this bug is uncomfortably dense. This is the second ASA/FTD zero-day exploited for DoS since August, when Cisco fixed CVE-2026-20349, an HTTP request processing flaw that similarly let unauthenticated attackers trigger reloads through the SSL VPN service. A year ago, September's ASA and FTD zero-days (CVE-2025-20362 and CVE-2025-20333) forced CISA's 24-hour Emergency Directive 25-03, in attacks Cisco linked to the ArcaneDoor campaign that had also been exploiting two older ASA zero-days since November 2023; earlier this month Cisco warned of an exploited Secure Email Gateway zero-day, CVE-2026-76519, that hands attackers root. Since November 2021, CISA has flagged 101 Cisco vulnerabilities as exploited in the wild — seven of them also used by ransomware crews. The perimeter box itself is a target category now, not just the thing that protects one.

What Should You Do?

  1. Upgrade to a fixed release now — the fixed ASA and FTD builds listed above are the only complete remediation, and the flaw is already exploited in the wild with no workaround available.
  2. Audit secondary authentication usage — check every tunnel group, including DefaultWEBVPNGroup, for secondary-authentication-server-group; devices without it are not on the affected processing path.
  3. If patching must wait, apply the mitigation knowingly — disabling secondary authentication or the tunnel group list cuts exposure but weakens VPN login security; treat it as a hours-to-days stopgap, not a fix.
  4. Inventory exposure and watch for unexplained reloads — an unexpected device reload on an SSL VPN firewall in the past weeks may be exploitation, not flaky hardware; check crash traces and open a TAC case if the timing fits.

The WAF Angle

There is no signature to write for this one, and that is the point. The crash lives inside the firewall's own tunnel-group authentication logic, reachable before any login succeeds — the network edge device that normally enforces policy is the thing being policy-attacked. This is the same shift we have tracked all year on exploited VPN and edge appliances: the Ivanti Connect Secure chain that rooted a fully patched VPN appliance, ransomware crews camping inside a patched Palo Alto GlobalProtect flaw, and Cisco's own October NX-OS wave of unauthenticated root bugs. A WAF in front of the web estate does nothing for the SSL VPN concentrator; the controls that matter here are patch velocity on the edge fleet, an accurate map of which management and VPN services face the internet, and availability monitoring that treats an unexplained reload as a security event rather than an operations nuisance.

Sources