It affects SSL remote access VPN. A remote attacker needs no login to make an affected device reload. Cisco rates it 8.6 High under CVSS 3.1 and confirmed active exploitation in October 2026.
What it allows
The flaw can stop the Remote Access SSL VPN service. Cisco links it to logic errors when a tunnel group uses secondary authentication. An attacker can send a crafted connection request to make the device reload. A successful VPN login is not required.
The Cisco CNA assigns CWE-690: an unchecked return value that leads to a NULL pointer dereference. The CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H.
That vector gives a High impact on service availability. It gives no impact on data secrecy or integrity. Cisco describes denial of service, not remote code execution.
Cisco PSIRT became aware of active exploitation in October 2026. The advisory appeared on October 28. It gives no exact day when attacks began. It names no attacker and gives no victim count.
The fetched CISA KEV catalog is dated October 28. It did not list this CVE when checked on October 29. That dated check does not cancel Cisco's direct warning that attackers are using the flaw.
Who is affected
The device must run an affected ASA or FTD release. Its SSL remote access VPN login service must be reachable. The relevant tunnel group must also use secondary authentication. Look for webvpn with SSL VPN enabled on an interface.
If tunnel-group-list enable is set, check every tunnel group for secondary-authentication-server-group. Include DefaultWEBVPNGroup. Check more than the profiles shown on the login page.
If the group list is absent or disabled, still check the default group. It can remain exposed when it uses secondary authentication.
For FTD, check the deployed remote access VPN policy and running setup. Use Firewall Management Center or Device Manager.
Cisco lists FMC itself and cloud-delivered FMC as not affected. It also lists Cloud-delivered Firewall and Secure Access as not affected. A managed firewall and its manager are distinct products.
ASA first fixed builds are 9.16.4.104 for 9.16 and earlier, and 9.18.4.96 for 9.18. Use 9.20.4.50 for 9.20, 9.22.3.200 for 9.22, and 9.23.1.48 for 9.23. For ASA 9.24, Cisco lists 9.24.1.27 or 9.24.10.1.
FTD first fixed builds are 7.0.11 for 7.0 and earlier, 7.2.13 for 7.2, and 7.4.9 for 7.4. Use 7.6.7 for 7.6 and 7.7.14 for 7.7. Use 10.0.3 for 10.0 and 10.1.1 for 10.1. Check Cisco's advisory and Software Checker for a build that suits the platform.
Use our Cisco ASA and FTD VPN DoS patch alert for the release table and setup checks. The patch management entry covers how to check a rollout. The vulnerability management entry explains how exposure and source evidence guide the risk decision.
Another Cisco Secure Firewall product carries a separate maximum-severity flaw. Cisco says CVE-2026-20079, an authentication bypass in Secure Firewall Management Center, was exploited, and CISA added it to KEV on 9 September 2026.
Timeline
- October 2026
Cisco PSIRT becomes aware of active exploitation; the advisory gives no exact start day.
- 28 Oct 2026
Cisco publishes advisory cisco-sa-asaftd-tunnel-dos-s6mgkb75 and the CNA record for CVE-2026-76418.
- 29 Oct 2026
This reference checks vendor conditions, fixed release tracks, and the fetched CISA KEV catalog.
- 29 Oct 2026
CISA adds CVE-2026-76418 to the Known Exploited Vulnerabilities catalog.
What to do
-
Find Reachable SSL VPN Services
Find ASA and FTD devices with reachable SSL remote access VPN. Record the product, running release, and enabled interface. Then check whether the advisory applies.
-
Inspect Every Relevant Tunnel Group
Check secondary-authentication-server-group in all groups when the group list is enabled. Always include DefaultWEBVPNGroup. Hiding the group list is not enough when the default group uses secondary authentication.
-
Upgrade on the Correct Release Track
Use the first fixed release for the deployed ASA or FTD track, or a later fixed build confirmed by Cisco. Check that the platform supports it. Plan the rollout, then check the running build.
-
Assess Temporary Mitigation Separately
Cisco documents a setup-specific mitigation and says there is no workaround. Removing secondary authentication lowers security. Disabling the group list changes profile selection. Assess each change with the remote access owner and choose fixed software when possible.
What Brandefense can do
- Watch your stack for exploited flaws
Name the vendors and products you run, and Brandefense alerts you when a CVE in them is exploited.
- See CVE-2026-76418 in Brandefense Atlas
The Atlas record of CVE-2026-76418: severity, exploitation status and the sources behind it.
- Vulnerability intelligence platform
Brandefense Vulnerability Intelligence follows which vulnerabilities attackers are using, so your team can patch what is under attack first.
Frequently Asked Questions
Is CVE-2026-76418 a remote code execution flaw?
Cisco describes unauthenticated remote denial of service through an unexpected device reload. Its CVSS 3.1 score is 8.6 High. The advisory does not describe remote code execution.
Does hiding the tunnel group list remove exposure?
Not when DefaultWEBVPNGroup uses secondary authentication. Cisco says to check that default group even when tunnel-group-list enable is absent or disabled.
Should secondary authentication be disabled on every VPN?
No. Cisco describes configuration-specific temporary mitigation and warns that removing secondary authentication lowers security. Assess the effect in the deployed environment and prioritize fixed software.
Sources
- ASA and FTD SSL VPN Tunnel DoS AdvisoryCisco PSIRT
- CVE-2026-76418 RecordCVE Program / Cisco CNA
- Known Exploited Vulnerabilities CatalogCISA