Skip to main content
All incident reports
Incident report

Cisco patches exploited Secure Firewall VPN flaw that lets attackers crash devices

Cisco has released fixes for CVE-2026-76418, a high-severity flaw in the Remote Access SSL VPN service of its Secure Firewall ASA and FTD software that unauthenticated attackers can use to force a device to reload. Cisco says the flaw has been exploited in the wild but has not said who is behind the attacks or whom they targeted.

· First published

The short version

  • The flaw. CVE-2026-76418, rated 8.6 on the CVSS scale, affects the Remote Access SSL VPN service in Cisco Secure Firewall Adaptive Security Appliance (ASA) and Secure Firewall Threat Defense (FTD) software. An unauthenticated attacker who sends a crafted request while connecting can make the device reload, causing a denial of service.
  • The cause. Cisco says the problem is logic errors that appear when secondary authentication is configured on a tunnel group, and that a successful VPN login is not needed to reach the affected code path. Exploitation also requires an unpatched release and a reachable SSL VPN login service.
  • Exploitation. Cisco's Product Security Incident Response Team learned in October 2026 that the flaw was being exploited. Cisco has published no indicators of compromise and has not described the attacks, the attackers or the targets.
  • Fixes and exposure. Fixes were released on 29 October and Cisco says there are no workarounds, only temporary mitigations that weaken remote access security. Shadowserver tracks more than 51,000 Cisco ASA SSL VPN devices exposed online, without saying how many are patched.

Timeline

DateEvent
August 2026Cisco fixes a separate denial-of-service zero-day, CVE-2026-20349, in the same ASA and FTD SSL VPN service.
October 2026Cisco's PSIRT becomes aware that CVE-2026-76418 is being exploited in the wild.
29 October 2026Cisco publishes an advisory and releases fixed ASA and FTD software releases for CVE-2026-76418.

What the vulnerability is

Cisco released software fixes on 29 October 2026 for CVE-2026-76418, a high-severity flaw in the Remote Access SSL VPN service of Secure Firewall ASA and FTD software. An unauthenticated, remote attacker who sends a crafted request while connecting to the SSL VPN can force the device to reload, interrupting availability. Cisco attributes the bug to logic errors that occur when secondary authentication is configured on a tunnel group.

Three conditions have to hold: an unpatched release is running, the SSL VPN login service is reachable, and secondary authentication is set in the tunnel group scope. Cisco says that where the tunnel group list is enabled, every group including the default DefaultWEBVPNGroup must be checked, and that disabling the list does not remove exposure if that default group uses secondary authentication. BleepingComputer describes affected devices as those with the webvpn keyword and SSL VPN enabled on at least one interface.

Exploitation and exposure

Cisco says its product security team learned in October 2026 that the flaw was being exploited. The company has not said when the attacks started, who is conducting them, which organisations were targeted or how many devices were hit, and it has not published indicators of compromise. SecurityWeek reports that the flaw came to light during a Cisco support case and that the company credited Eric Fernald with finding it.

Much of the internet-facing estate is easy to count. Internet monitoring service Shadowserver tracks more than 51,000 Cisco ASA SSL VPN devices exposed online, according to BleepingComputer, though the platform does not show how many have been secured or are decoys. That figure covers ASA devices only and says nothing about how many meet the configuration the vulnerability needs.

Mitigation and earlier Cisco VPN flaws

Cisco offers no workaround that removes the flaw; it recommends upgrading to a fixed release and points customers to its advisory for the version list. Administrators who cannot patch at once can turn off the tunnel group list if the default group does not use secondary authentication, or remove secondary authentication from user-configured groups or from DefaultWEBVPNGroup. Cisco warns that dropping secondary authentication makes remote access VPN less secure. On FTD, the deployed remote access VPN policy and running configuration should be reviewed in Cisco Secure Firewall Management Center or the device manager.

This is the second exploited denial-of-service zero-day in the same ASA and FTD SSL VPN service since August, when Cisco fixed CVE-2026-20349, an HTTP request processing flaw that also allowed unauthenticated attackers to trigger a reload. Cisco gave no detail on those attacks either, and SecurityWeek notes it is unclear whether one actor is behind both. BleepingComputer additionally recalls the September 2025 fixes for CVE-2025-20362 and CVE-2025-20333, which Cisco linked to the ArcaneDoor campaign against firewall devices.

What is not known yet

  • Who is exploiting CVE-2026-76418, and whether the same actor carried out the August attacks on the same service.
  • Which organisations and how many devices have been targeted, and when exploitation began before October.
  • Whether any attack caused operational outage beyond a device reload.
  • How many of the internet-exposed ASA and FTD devices remain unpatched or misconfigured for secondary authentication.
  • Whether the attackers used this flaw alone or in combination with other access.

What to do

If you run Cisco Secure Firewall ASA or FTD with SSL VPN

  1. Establish whether SSL VPN is enabled on any interface and whether secondary authentication is set in any tunnel group, including DefaultWEBVPNGroup.
  2. Upgrade to a fixed software release; take the version for your release train from Cisco's advisory.
  3. If you cannot upgrade immediately, remove secondary authentication from user-configured tunnel groups and the default group, or disable the tunnel group list where the default group does not use secondary authentication, and schedule the upgrade because Cisco says this weakens remote access security.
  4. On FTD, review the deployed remote access VPN policy and the resulting running configuration in the management centre or device manager.

For network operations teams

  1. Treat an unplanned reload of an internet-facing ASA or FTD device with SSL VPN enabled as something to investigate, since Cisco has published no indicators of compromise.
  2. Record which of your VPN endpoints meet all three exploitation conditions, so patching can be prioritised if a device is missed.

For everyone else

  1. Keep an inventory of internet-facing VPN and remote-access appliances and their firmware versions, because these devices are repeatedly the target of unauthenticated denial-of-service and access flaws.
  2. Apply vendor fixes for flaws reported as exploited without waiting for a maintenance window.

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.