Exploited now
Remediation guideCVE-2026-76418
Cisco Secure Firewall Adaptive Security Appliance and Secure Firewall Threat Defense Software Remote Access SSL VPN Tunnel Denial of Service Vulnerability
- CISA KEV
- Known exploitedadded 29 Oct 2026; US federal deadline 1 Nov 2026
- Exploit likelihood
- 0.82%58th percentile · FIRST EPSS, 2026-11-15
- Severity
- 8.6 HighCVSS 3.1, Cisco
- Last verified
- 30 Oct 2026against the sources below
1In plain language
A flaw in the SSL remote access VPN service of Cisco's ASA and FTD firewall software lets an attacker on the network, without logging in, make the device reload unexpectedly: a denial of service.
It comes from logic errors when secondary authentication is configured on a tunnel group.
Cisco became aware of active exploitation in October 2026, and CISA lists it as known to be exploited.
2Am I affected?
A device is affected if all three are true: it runs a vulnerable release of ASA or FTD software, its SSL remote access VPN login service is reachable, and secondary authentication is configured in the tunnel group scope.
Cisco has confirmed it does not affect Cloud-delivered Firewall (CDFW), Cloud-delivered Firewall Management Center (cdFMC), Secure Access (CSA) or Secure FMC Software.
Cisco's fix tables list release trains with the first release that includes the fix.
Affected releases include ASA 9.19 and FTD 7.3, but Cisco's fix tables leave them out; some builds numbered above their first fixed release are also listed as affected: see Fix. our analysis
Affected releases are summarised by release train in the Fix table.
Check your version
A command to show the running software release: Not stated by vendor.
Cisco provides the Cisco Software Checker to find the advisories that affect a specific software release, and the earliest release that fixes them. Source ↗
Then check the configuration. SSL remote access VPN: Cisco says the configuration is vulnerable if the running configuration contains the webvpn keyword and SSL VPN is enabled on at least one interface.
webvpn enable <interface_name>
Lines to look for in the running configuration, as the vendor shows them.
On FTD, remote access VPN is enabled from Devices > VPN > Remote Access in Secure Firewall Management Center (FMC), or from Remote Access VPN in Secure Firewall Device Manager (FDM).
That alone isn't enough to be affected: secondary authentication must also be configured on a tunnel group, as checked below. our analysis
Tunnel groups: if tunnel-group-list enable is configured, check all tunnel groups, including the default tunnel group, DefaultWEBVPNGroup, for secondary-authentication-server-group. This isn't limited to the profiles shown in the group list on the login page.
If tunnel-group-list enable is absent, or was removed with no tunnel-group-list enable, still check DefaultWEBVPNGroup for secondary-authentication-server-group: disabling the group list doesn't remove exposure when that default group uses secondary authentication.
On FTD, review the deployed remote access VPN policy and the resulting device running configuration in FMC or FDM. A successful VPN login is not required to reach the affected processing path.
3Fix
Cisco bug ID: CSCwx26625.
Cisco strongly recommends upgrading to the fixed software in this table. Cisco's PSIRT validates only the affected and fixed release information documented in the advisory.
Cisco's record also lists ASA 9.19 and FTD 7.3 releases as affected, but Cisco's own fix tables leave those trains out, so Cisco gives no fixed release for them (shown below as 'Not stated by vendor').
If you run 9.19 or 7.3, use the Cisco Software Checker to find a fixed release to move to. Releases that are in neither Cisco's table nor its record (for example ASA 9.17) aren't listed as affected; confirm with the Software Checker. our analysis
Cisco's record also lists 9.18.4.135, 9.20.4.235, 9.23.1.195 and 9.24.1.155 as affected, although they're numbered above the first fixed release for their train.
Check your exact build with the Cisco Software Checker rather than comparing version numbers. our analysis Link ↗
| Product | Release | First fixed release |
|---|---|---|
| Cisco Secure Firewall ASA Software | 9.16 and earlier | 9.16.4.104 |
| 9.18 | 9.18.4.969.18.4.135 is also listed as affected: check your build with the Cisco Software Checker. our analysis | |
| 9.19 | Not stated by vendor: affected per the vendor's record; this train is not in the vendor's fix table | |
| 9.20 | 9.20.4.509.20.4.235 is also listed as affected: check your build with the Cisco Software Checker. our analysis | |
| 9.22 | 9.22.3.200 | |
| 9.23 | 9.23.1.489.23.1.195 is also listed as affected: check your build with the Cisco Software Checker. our analysis | |
| 9.24 | 9.24.1.27 / 9.24.10.19.24.1.27 for 9.24.1 builds, 9.24.10.1 for 9.24.10. 9.24.1.155 is also listed as affected: check your build with the Cisco Software Checker. our analysis | |
| Cisco Secure FTD Software | 7.0 and earlier | 7.0.11 |
| 7.2 | 7.2.13 | |
| 7.3 | Not stated by vendor: affected per the vendor's record; this train is not in the vendor's fix table | |
| 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 |
4Can't patch tonight?
There are no workarounds. There is a mitigation: disable secondary authentication on any user-configured tunnel group list or on the default tunnel group, DefaultWEBVPNGroup.
Cisco describes two cases:
- If DefaultWEBVPNGroup does not use secondary authentication, disable the tunnel group list: in WebVPN configuration mode, enter no tunnel-group-list enable. Users can then no longer choose a connection profile from a list, and need to know the correct profile to use.
- If DefaultWEBVPNGroup uses secondary authentication, remove it with the no secondary-authentication-server-group command. With secondary authentication disabled, the security posture for remote access VPN is lowered.
Cisco says the mitigation was proven in a test environment: evaluate its applicability and effectiveness in your own environment before deploying it, because it may affect the functionality, performance or security posture of your network.
Our reading of Cisco's check section: while the tunnel group list is enabled, every tunnel group counts, so remove secondary authentication from each one that uses it, not only DefaultWEBVPNGroup. our analysis
How to apply the mitigation on FTD managed by FMC or FDM: Not stated by vendor.
Cisco considers workarounds and mitigations temporary solutions until you can upgrade to a fixed release.
5Was I hit?
Logs to check, detection steps and indicators of compromise: Not stated by vendor.
A successful attack could cause the device to reload.
An unexpected reload of an ASA or FTD device with one of these configurations is worth investigating, but a reload alone doesn't show the device was attacked. our analysis
CISA's catalog does not mark forensic triage as required for this CVE.
6Sources
- Cisco Secure Firewall Adaptive Security Appliance and Secure Firewall Threat Defense Software Remote Access SSL VPN Tunnel Denial of Service VulnerabilityCisco · primary source
- Known Exploited Vulnerabilities catalog: CVE-2026-76418CISA
- CVE-2026-76418NVD
- Exploit Prediction Scoring System (EPSS)FIRST · exploit likelihood, updated daily
Summary of public vendor guidance. Verify against the vendor advisory before acting.
See CVE-2026-76418 in the exploited-now list (exploit likelihood, CISA's description, deadline).
More Cisco guides
- CVE-2026-20079Cisco FMC authentication bypass
- CVE-2026-20349Cisco ASA/FTD SSL VPN denial of service (HTTP requests)
- CVE-2026-76460Cisco ISE authentication bypass
- CVE-2026-76461Cisco Secure Email Gateway SQL injection
- CVE-2026-76504Cisco SD-WAN Manager API authentication bypass
- CVE-2026-76519Cisco Secure Email Gateway file write (AMP)