CVE-2026-76418
Cisco ASA and FTD remote access SSL VPN denial of service, exploited in the wild and on CISA KEV with a Nov 1 deadline; exposed only when secondary authentication is set on a tunnel group
Reachable if an ASA or FTD in the affected range has SSL VPN enabled on a reachable interface and secondary authentication set on any tunnel group
CVE-2026-76418 is a denial of service, not code execution. Someone without a login can send a crafted request to the Remote Access SSL VPN login service on a Cisco Secure Firewall ASA or FTD device and make the device reload, which drops every VPN session and every connection through the firewall until it comes back. Cisco says it is aware of active exploitation, and CISA added it to the Known Exploited Vulnerabilities catalog on October 29, 2026 with a federal due date of November 1. Cisco scores it 8.6, below the 9.0 bar we normally use; it is here because it is on KEV and because the fix is a reboot-and-reload cycle on a device that sits in front of everything else.
A device is exposed only when two things are true. SSL VPN (webvpn) is enabled on an interface that attackers can reach, and secondary authentication is configured on a tunnel group, including the default one. That makes this one of the easiest advisories on this page to check. Cisco has released fixed software for every ASA and FTD train. It says no workaround addresses the flaw and offers a mitigation that removes secondary authentication, which lowers VPN security, so treat that as a last resort.
Is it reachable for you?
What it is. Cisco's advisory describes logic errors in how the SSL VPN login service handles a connection when secondary authentication is configured on a tunnel group. A crafted request during the connection reaches the affected code path before any login succeeds (Cisco: "a successful VPN login is not required to reach the affected processing path"), triggers a NULL pointer dereference (CWE-690), and the device reloads. Cisco's vector scores confidentiality and integrity as None; the impact is availability only. Cisco credits Eric Fernald, who found it during a TAC support case, and tracks it as bug CSCwx26625. CISA's entry marks forensic triage as not required, unlike the GitLab listing from the same day.
Not to be confused with. Other Cisco ASA and FTD flaws on CISA KEV that turn up in the same searches, each with its own advisory and fix. CVE-2026-20349 (ASA/FTD, added August 11, 2026). CVE-2025-20333 and CVE-2025-20362 (ASA/FTD, added September 25, 2025). CVE-2024-20481 (ASA/FTD denial of service, added October 24, 2024). CVE-2024-20353 and CVE-2024-20359 (added April 24, 2024). CVE-2023-20269 (added September 13, 2023). The Secure Firewall Management Center entries on KEV (CVE-2026-20079, CVE-2026-20316, CVE-2026-20131) affect FMC, which Cisco says is not affected by this CVE. Being patched for any of those does not cover CVE-2026-76418.
Checks, in order. Run these on devices your organization manages. They read configuration and change nothing. All three of the first conditions must be true for a device to be exposed.
- Which release are you on?
show versionon ASA, or the device page in FMC or FDM. Compare against the first fixed releases below. Cisco's Software Checker returns the combined first fixed release if you also need to clear other ASA or FTD advisories. - Is SSL VPN enabled? On ASA, run
show running-config webvpn. The device is in scope if the output containswebvpnwithenable <interface_name>on at least one interface. If no interface is enabled, stop here; the device is not exposed to this flaw. On FTD, remote access VPN is enabled from Devices, VPN, Remote Access in FMC, or Remote Access VPN in FDM. - Is secondary authentication configured on any tunnel group? This is the check that decides it. Run
show running-config tunnel-groupand look forsecondary-authentication-server-group. Per Cisco's advisory, iftunnel-group-list enableis present under webvpn, check every tunnel group includingDefaultWEBVPNGroup; Cisco says the check "is not limited to profiles that are displayed in the group list on the login page." Iftunnel-group-list enableis absent or was removed, still checkDefaultWEBVPNGroup; Cisco says disabling the group list does not remove exposure when that default group uses secondary authentication. On FTD, review the deployed remote access VPN policy and the resulting running configuration, since a policy edited but not deployed doesn't count. - Is the login page reachable from outside? Confirm from outside your network which interfaces serve the SSL VPN login portal. Remote access VPN exists to be reached from the internet, so assume yes unless you've proven otherwise.
- Look for unexpected reloads since disclosure. Cisco reports exploitation in October 2026. Check
show versionfor uptime and the last reload reason on each ASA, and review FMC health events and your syslog or SIEM for unplanned reboots or failovers in October. - What depends on this device? A reload takes down not just VPN users but every flow through the firewall and any failover pair's active unit. Note what sits behind it and how long a reload takes on your hardware.
First fixed releases, from Cisco's advisory.
- ASA: 9.16 and earlier, 9.16.4.104. 9.18, 9.18.4.96. 9.20, 9.20.4.50. 9.22, 9.22.3.200. 9.23, 9.23.1.48. 9.24, 9.24.1.27 and 9.24.10.1.
- 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. 10.1, 10.1.1.
- Not vulnerable, per Cisco: Cloud-delivered Firewall, cloud-delivered FMC, Secure Access, and Secure FMC Software itself.
Compensating controls (test them, don't assume them)
Cisco says no workaround addresses the vulnerability. These reduce exposure while you schedule the upgrade, and each one works only under the condition at the end of its line. Test on one device before rolling out.
- Delivery. Limit which source networks can reach the SSL VPN login portal, and remove webvpn from interfaces that don't need it. An attacker needs only to reach the portal, with no login. This shrinks who can send the crafted request, only if the restriction is enforced upstream of the device, covers every interface with webvpn enabled, and your users can still connect. Most remote access deployments can't do this, which is why Cisco doesn't list it.
- Exploitation, Cisco's mitigation case 1. If
DefaultWEBVPNGroupdoes not use secondary authentication, enterno tunnel-group-list enablein webvpn configuration mode. Per Cisco, users "will no longer be able to choose a connection profile (the tunnel-group name) from a provided list and instead will need to know the correct profile to use." This takes the vulnerable condition out of the reachable path, only ifDefaultWEBVPNGrouptruly has nosecondary-authentication-server-group, which you confirm withshow running-config tunnel-groupafter the change. - Exploitation, Cisco's mitigation case 2. If
DefaultWEBVPNGroupuses secondary authentication, runno secondary-authentication-server-groupto remove it. Per Cisco, "the security posture is lowered for remote access VPN." You are removing a second factor from VPN login to avoid an outage; decide that with whoever owns the risk. Cisco says the mitigation "was proven successful in a test environment" and should be evaluated in your own first. This removes the vulnerable configuration, only if your identity team accepts the loss of the second factor and, on FTD, the change survives the next policy deployment from FMC. - Blast radius. Confirm high availability or failover is configured and tested, keep an alternate path for remote administration and critical remote access, and alert on device reloads and failover events. This shortens the outage, only if the standby unit is also patched or mitigated, failover was tested recently, and the alternate path does not depend on the affected device.
The patch is the only fix. Upgrade to ASA 9.16.4.104, 9.18.4.96, 9.20.4.50, 9.22.3.200, 9.23.1.48, 9.24.1.27 or 9.24.10.1, or FTD 7.0.11, 7.2.13, 7.4.9, 7.6.7, 7.7.14, 10.0.3 or 10.1.1, matching your release train.
What to look for in logs
Cisco and CISA have published no request signatures, addresses or other indicators for this CVE as of October 30, 2026. The observable effect Cisco describes is an unexpected device reload, so these are what to watch, only if the devices forward syslog to a system that alerts on them.
- Unexpected reloads of an ASA or FTD device with SSL VPN enabled. Check
show versionfor the last reload reason and uptime, andshow crashinfoon ASA. - Crash files or core dumps on the device following connection attempts to the VPN login page.
- Bursts of SSL VPN connection attempts that never complete a login, especially shortly before a reload.
- A failover pair switching active units, or mass VPN session drops, without a planned change.
FAQ
Does CVE-2026-76418 let an attacker into my network?
No. It is a denial of service. The device reloads, which drops VPN sessions and traffic through the firewall until it recovers. Cisco's vector scores confidentiality and integrity impact as None, and the advisory describes no code execution or data access.
Is CVE-2026-76418 being exploited?
Yes. Cisco's advisory says the Cisco PSIRT became aware of active exploitation in October 2026, and CISA added the CVE to its Known Exploited Vulnerabilities catalog on October 29, 2026 with a November 1 due date.
Am I exposed if I don't use secondary authentication on my VPN?
Per Cisco, no. The flaw is reached only when secondary authentication is configured on a tunnel group, including the default group. Check every tunnel group, not only the ones users see on the login page.
Does disabling the tunnel group list fix CVE-2026-76418?
Not on its own. Cisco says no tunnel-group-list enable helps only when DefaultWEBVPNGroup does not use secondary authentication. If it does, the mitigation is no secondary-authentication-server-group, which lowers VPN security. Upgrading is the only fix.
Why is an 8.6 on this page?
Our bar is Critical or on CISA KEV. This one is on KEV with confirmed exploitation, and the thing that goes down is the device everything else sits behind.
Is CVE-2026-76418 the same as the 2025 Cisco ASA zero-days?
No. CVE-2025-20333 and CVE-2025-20362 are separate ASA and FTD flaws added to KEV on September 25, 2025. CVE-2026-76418 is a separate denial of service flaw disclosed October 28, 2026.
- Vendor
- Cisco
- Product
- Secure Firewall ASA Software and Secure Firewall Threat Defense (FTD) Software
- Affected versions
- ASA before 9.16.4.104, 9.18.4.96, 9.20.4.50, 9.22.3.200, 9.23.1.48, 9.24.1.27 / 9.24.10.1; FTD before 7.0.11, 7.2.13, 7.4.9, 7.6.7, 7.7.14, 10.0.3, 10.1.1. Only when SSL VPN is enabled and secondary authentication is configured on a tunnel group
- Vulnerable component
- Remote Access SSL VPN login service (webvpn) with secondary-authentication-server-group on a tunnel group
- CVSS
- 8.6 (Cisco as CNA); NVD has not added its own score. Published here because it is on CISA KEV, not for its score
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H (Cisco)
- CWE
- CWE-690 Unchecked Return Value to NULL Pointer Dereference
- Exploitation
- Confirmed (CISA KEV)
- CISA KEV added
- October 29, 2026
- Patch
- Cisco advisory cisco-sa-asaftd-tunnel-dos-s6mgkb75 (Oct 28, 2026), bug ID CSCwx26625. Fixed releases per train in the body. Cisco says no workaround addresses the flaw; it offers a mitigation that lowers VPN security
Updates
Oct 30, 2026. Controls rewritten in the stage and "only if" format; added the full list of other Cisco ASA, FTD and FMC entries on KEV, and Cisco's Software Checker note. No change to status or fixed releases.
Oct 29, 2026. First published, the day CISA added the CVE to KEV. Cisco published the advisory Oct 28.
Sources
- Cisco Security Advisory cisco-sa-asaftd-tunnel-dos-s6mgkb75 (Oct 28, 2026)
- CISA Known Exploited Vulnerabilities catalog (CVE-2026-76418 added Oct 29, 2026, due Nov 1; checked in the JSON feed, catalog 2026.10.29)
- NIST NVD: CVE-2026-76418 (shows Cisco's 8.6; no NVD score yet)
We publish an advisory when a vulnerability is Critical or on CISA KEV, has one identifiable component to check, and has a public proof of concept or reported exploitation. Advisories are updated as exploitation status changes.