An exploited flaw in the Remote Access SSL VPN service of Cisco Secure Firewall ASA and Secure Firewall Threat Defense (FTD) lets an attacker with no login crash and reload the firewall. A device is affected if it runs a vulnerable release, its SSL VPN login service is reachable, and secondary authentication is configured in the applicable tunnel group.
Find your fixed releaseCVE-2026-76418 is a denial-of-service flaw (CVSS 3.1 score 8.6, High) in the Remote Access SSL VPN service of Cisco ASA and FTD software. An unauthenticated, remote attacker can send a crafted request while connecting to the SSL VPN and make the firewall reload. Confirm a fixed release for your exact build and platform in Cisco Software Checker. Cisco lists fixed releases such as ASA 9.20.4.50, 9.22.3.200 or 9.24.1.27, or FTD 7.4.9, 7.6.7 or 10.0.3.
Cisco became aware of active exploitation in October 2026. CISA added CVE-2026-76418 to its Known Exploited Vulnerabilities catalog on October 29, 2026, and the catalog lists November 1, 2026 as the due date. US federal civilian agencies should determine the applicable timeline for each asset under BOD 26-04. Cisco lists no workaround and recommends upgrading to a fixed release. If you cannot upgrade immediately, evaluate the impact on your VPN users and security before applying the temporary mitigation. Removing secondary authentication weakens VPN security. If DefaultWEBVPNGroup does not use secondary authentication, disable the tunnel group list. If the default group uses secondary authentication, remove it from that group. If you keep the list enabled, remove secondary authentication from every affected tunnel group.
From the Cisco Security Advisory cisco-sa-asaftd-tunnel-dos-s6mgkb75 (version 1.0, published October 28, 2026). Check your exact build in Cisco Software Checker. Build numbers alone can mislead. Cisco’s CVE record lists ASA 9.18.4.135, 9.20.4.235, 9.23.1.195, and 9.24.1.155 as affected, even though their build numbers are higher than the first fixed builds shown for their trains.
| Software | Release train | First fixed release |
|---|---|---|
| Cisco Secure Firewall ASA | 9.16 and earlier | 9.16.4.104 If you manage the device with ASDM, verify that you have Cisco-signed ASDM 7.18(1)152 or later before upgrading. The fixed ASA build rejects older ASDM images. |
| 9.18 | 9.18.4.96 | |
| 9.20 | 9.20.4.50 | |
| 9.22 | 9.22.3.200 (custom release based on 9.22.3.26) | |
| 9.23 | 9.23.1.48 | |
| 9.24 | 9.24.1.27 for the 9.24.1 branch 9.24.10.1 for the 9.24.10 branch. ASA Virtual must pass through 9.24(1) before upgrading to a later release and cannot downgrade below 9.24(1) once upgraded. ASA 9.24 removes IKEv1 IPsec-over-TCP support. If you use it, plan a migration first or choose a fixed release on an earlier branch. | |
| Cisco Secure FTD | 7.0 and earlier | 7.0.11 |
| 7.2 | 7.2.13 | |
| 7.4 | 7.4.9 | |
| 7.6 | 7.6.7 | |
| 7.7 | 7.7.14 | |
| 10.0 | 10.0.3 (build 500 for Secure Firewall 200, build 1 for other supported FTD devices) | |
| 10.1 | 10.1.1 (build 500 for Secure Firewall 200, build 1 for other supported FTD devices) | |
| Not affected | Cloud-delivered Firewall (CDFW), Cloud-delivered Firewall Management Center (cdFMC), Secure Access (CSA), Secure FMC Software | |
The flaw is in the SSL VPN service that AnyConnect and Secure Client users connect to, not in the client software.
Cisco says the vulnerability in the Remote Access SSL VPN service of ASA and FTD software “could allow an unauthenticated, remote attacker to cause the device to reload unexpectedly, resulting in a denial of service (DoS) condition.” The cause is “logic errors when secondary authentication is configured on a tunnel group.” An attacker sends a crafted request when connecting to the SSL remote access VPN, and the device reloads.
The weakness is classed as CWE-690, an unchecked return value that leads to a NULL pointer dereference. Cisco rates it High with a CVSS 3.1 base score of 8.6: network attack, low complexity, no privileges, no user interaction, and a high impact on availability. It is a crash, not code execution. The advisory says nothing about data being read or changed.
A device is affected only when all three of these are true, according to Cisco:
webvpn keyword and SSL VPN is enabled on at least one interface.Cisco adds that “a successful VPN login is not required to reach the affected processing path.” Anyone who can reach the VPN login page can try it. The advisory says the flaw was found during the resolution of a Cisco TAC support case.
The conditions come from the advisory. The commands are standard ASA CLI; on FTD, Cisco says to review the deployed remote access VPN policy in FMC or FDM.
On an ASA, the first lines of this command show the software version:
show version
On FTD, check the Threat Defense version in FMC or FDM, or run show version in the FTD CLI. Do this for every device, including both units of a failover pair. Check your exact release and platform in Cisco Software Checker, including any train missing from the table. Follow the upgrade guide and release notes for your chosen target to check compatibility and any required intermediate upgrades or post-upgrade tasks. On a Firepower 1010 upgrading from FTD 7.4.x or earlier to FTD 7.6 or later, move any VLAN 1 subinterface to a different VLAN ID before upgrading. The upgrade removes VLAN 1 from the subinterface.
For ASA VPN load-balancing clusters, check the ASA upgrade guide for your upgrade path. Cisco documents the mixed-version restriction on the 9.16, 9.18, 9.20, 9.22, 9.23, and 9.24 trains. Where it applies, plan for VPN load balancing to be unavailable until all members run the same version. Cisco’s hitless procedure temporarily removes the keys from every member, leaving the load-balancing cluster unauthenticated. Keep that interval as short as possible and restore the keys on every member after upgrading.
For FMC-managed FTD remote access VPN load-balancing groups, check whether your upgrade crosses Cisco’s secure-communications requirement. If it does, enable IPsec encryption, set an encryption key, and deploy the policy before upgrading. Upgrade the entire group. Cisco does not support leaving the group on mixed versions across this upgrade boundary. During the transition, new VPN connections can be load-balanced only to members on the same side of the upgrade as the director. Make sure those members have enough capacity. If you upgrade an FTD device running Universal ZTNA from 7.7.10 through 10.0.x to 10.1.1, deploy from FMC after the upgrade to restore Universal ZTNA traffic. FTD Virtual cannot revert from Version 10 or later to 7.7 or earlier.
show running-config webvpn
If the output contains enable followed by an interface name, SSL VPN is enabled on that interface. If there is no webvpn section or no interface is enabled, the SSL VPN configuration condition is unmet. If an interface is enabled, confirm whether the SSL VPN login service is reachable through it. On FTD, remote access VPN is set up under Devices > VPN > Remote Access in FMC, or under Remote Access VPN in FDM.
In the same webvpn output, look for tunnel-group-list enable, then check the tunnel groups:
show running-config all tunnel-group
See Cisco’s ASA connection profile guide for how this command displays configured and default profile settings.
tunnel-group-list enable is present: check every tunnel group, including the default DefaultWEBVPNGroup, for secondary-authentication-server-group. Cisco notes the check is not limited to the profiles shown in the group list on the login page.tunnel-group-list enable is absent: check DefaultWEBVPNGroup for secondary-authentication-server-group. Cisco says disabling the group list does not remove exposure when the default group uses secondary authentication.Check whether the setting actually enables secondary authentication. Cisco documents that secondary-authentication-server-group none means secondary authentication is not required. Cisco’s exposure criteria are a vulnerable release, a reachable SSL VPN login service, and secondary authentication configured in the applicable tunnel group scope.
Cisco says there are no workarounds. Its mitigation removes the exposure to secondary authentication, and Cisco treats it as temporary.
Disable the tunnel group list. In WebVPN configuration mode, Cisco’s command is:
webvpn
no tunnel-group-list enable
Side effect: users can no longer pick a connection profile (tunnel group) from a list on the login page. They will need to know the correct profile to use.
Removing secondary authentication weakens remote access VPN security. Evaluate that impact before changing production. To apply Cisco’s temporary mitigation, use no secondary-authentication-server-group. The advisory names only the command; Cisco’s ASA configuration guides place it in the tunnel group’s general-attributes mode:
tunnel-group DefaultWEBVPNGroup general-attributes
no secondary-authentication-server-group
If you keep the tunnel group list enabled, remove configured secondary authentication from every affected tunnel group, including DefaultWEBVPNGroup. If you disable the list, remove secondary authentication from DefaultWEBVPNGroup as well.
After applying either ASA mitigation, verify the running configuration and test VPN login with the intended connection profiles. Save the verified configuration to startup configuration with write memory so the mitigation survives a reload. Once every affected unit is running a fixed release, restore the tunnel group list and secondary authentication settings you changed, test VPN login again, and save the restored configuration.
The advisory gives the mitigation as ASA CLI commands and does not describe FMC or FDM steps. On FTD, review the deployed remote access VPN policy and the resulting device running configuration, as Cisco advises, and ask Cisco TAC if you are unsure how to apply the change. Cisco says the mitigation “has been deployed and was proven successful in a test environment,” but asks customers to check its applicability and impact in their own network first, and strongly recommends upgrading to a fixed release.
Cisco’s advisory lists no CVE-specific indicators of compromise. An unexpected reload is a reason to investigate and can have several causes. Use the commands below to check firewall-engine uptime and collect crash information.
show version on ASA or show version system on FTD. If a firewall with SSL VPN enabled restarted unexpectedly, investigate the cause.show crashinfo in privileged EXEC mode to read the latest saved crash file. Compare its timestamp with the reload you are investigating and preserve any matching file for Cisco TAC. On FTD, use Cisco’s crash data collection instructions to preserve existing crash information and core files for TAC. Do not force a crash yourself: Cisco documents crashinfo force only as a diagnostic step under TAC supervision, and a crash usually reloads the firewall.If you find a reload you can’t explain, open a Cisco TAC case, give them the crash information, and upgrade or apply the mitigation right away. CISA’s catalog entry does not flag this CVE for forensic triage under its federal patching directive.
| Date | Event |
|---|---|
| October 2026 | Cisco PSIRT becomes aware of active exploitation of the vulnerability. |
| October 28, 2026 | Cisco publishes advisory cisco-sa-asaftd-tunnel-dos-s6mgkb75 (version 1.0) with fixed releases. The CVE-2026-76418 record is published. |
| October 29, 2026 | CISA adds CVE-2026-76418 to the Known Exploited Vulnerabilities catalog. |
| November 1, 2026 | Due date in CISA’s KEV catalog. Federal civilian agencies should assess each asset’s internet exposure and follow the applicable BOD 26-04 remediation timeline. Follow Cisco’s mitigation instructions while arranging an upgrade. CISA also directs agencies to follow applicable BOD 26-04 guidance for cloud services or discontinue use if mitigation is unavailable. |
A known-attacker list helps against password guessing at the VPN login. It does not fix this flaw.
CVE-2026-76418 can be exploited without a VPN login when the affected service is reachable. Upgrade to a fixed release. Use Cisco’s temporary mitigation if you cannot upgrade immediately. No block list replaces either step, and an attack from an address that is not on a list is not affected by it.
ThreatListPro is a plain-text IPv4 feed designed to reduce VPN password guessing from listed addresses. The feed covers 5.4M+ IPv4 addresses and is checked for new attackers every 6 hours. Its entries come from real attacks on live production Palo Alto GlobalProtect VPN portals in the US. On ASA, use an inbound control-plane ACL on the interface that receives VPN connections to deny new connections from listed source addresses. Follow Cisco’s control-plane ACL instructions.
Yes. Cisco says its PSIRT became aware of active exploitation in October 2026. CISA added CVE-2026-76418 to its Known Exploited Vulnerabilities catalog on October 29, 2026, and the catalog lists November 1, 2026 as the due date. US federal civilian agencies should determine the applicable timeline for each asset under BOD 26-04.
The first fixed ASA releases are 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 or 9.24.10.1 on the 9.24 train. The first fixed FTD releases are 7.0.11, 7.2.13, 7.4.9, 7.6.7, 7.7.14, 10.0.3 and 10.1.1. Releases older than ASA 9.16 or FTD 7.0 should move to a fixed release. Confirm your exact build in Cisco Software Checker, since Cisco lists some higher-numbered ASA builds as affected.
The flaw is in the Remote Access SSL VPN service on the ASA or FTD firewall, the head end that AnyConnect and Secure Client users connect to. Cisco’s advisory does not list the client software as affected. The fix is an upgrade of the firewall software.
No. Cisco describes an unauthenticated, remote attacker who sends a crafted request when connecting to the SSL remote access VPN, and says a successful VPN login is not required to reach the affected code. A successful exploit can reload the firewall, interrupting traffic and potentially dropping VPN sessions.
According to Cisco, a device is affected only when it runs a vulnerable release, the SSL remote access VPN login service is reachable, and secondary authentication is configured in the tunnel group scope the advisory describes. If tunnel-group-list enable is on, check every tunnel group, including DefaultWEBVPNGroup. If it is off, check DefaultWEBVPNGroup. Cisco still recommends upgrading.
Cisco lists no workaround and gives a temporary mitigation. If DefaultWEBVPNGroup does not use secondary authentication, disable the tunnel group list. If DefaultWEBVPNGroup uses secondary authentication, remove it from that group. If you leave the list enabled, remove configured secondary authentication from every affected tunnel group. Removing secondary authentication weakens remote access VPN security. Upgrade to a fixed release as soon as possible.
Cisco’s advisory publishes no IP addresses or other indicators. The visible effect of an attack is an unexpected reload of the firewall, so check device uptime and crash information, and open a Cisco TAC case if an ASA or FTD with SSL VPN enabled reloaded without a known cause.
ThreatListPro covers 5.4M+ IPv4 addresses and is checked for new attackers every 6 hours, as a plain-text IPv4 feed. Monthly is $19.99 with a 14-day free trial and no card needed.
Start a 14-day free trial Or test the free sample first: no signupThreatListPro uses a plain-text feed for firewalls that support external IPv4 address lists.
More on Cisco VPN hardening and the other exploited flaws we track.