Cisco Secure Firewall ASA and FTD: exploited VPN flaw, update now
Cisco has fixed a flaw (CVE-2026-76418) in the remote access VPN of its Secure Firewall ASA and Secure Firewall Threat Defense (FTD) software. Someone on the internet who has no password can send a request that makes the firewall restart unexpectedly, which takes it out of service. Cisco says it knows of attacks using this flaw, and CISA, the US cybersecurity agency, added it to its list of exploited vulnerabilities on 29 October 2026. It concerns any company whose firewall runs this software with the SSL VPN and a second login step, and because attacks are under way, the question of whether you are affected should be answered today.
Does this affect you?
You have this product if your office firewall is a Cisco ASA or a Cisco Secure Firewall (Firepower) device, or if your IT provider runs Cisco Secure FTD software on it. Check the purchase invoices or the support contract, or ask the person or company that set up your internet connection. The flaw matters only when three things are true: the firewall runs an affected release, the SSL VPN login used by remote staff can be reached from outside, and secondary authentication (a second login check for VPN users) is set up. Cisco says the check must cover every VPN connection profile, including the default one, not only those shown on the login page. Cisco also says its cloud-delivered firewall service, cloud-delivered Firewall Management Center, Secure Access and Secure FMC software are not affected.
What to do
- Ask whoever manages your firewall whether it is a Cisco ASA or Secure FTD device with the SSL remote access VPN turned on and a second login check set up.
- If it is, have them upgrade to the fixed version for your line, listed under What we know. If your line is not listed there, it may still be affected: Cisco’s record names ASA 9.19 releases as affected but gives no fixed 9.19 version, so ask them to check Cisco’s advisory or the Cisco Software Checker for a fixed release to move to.
- Ask for the update to be scheduled today, since Cisco reports attacks in the wild.
- If the update cannot happen today, ask them to consider Cisco’s temporary mitigation described below, after confirming it suits your setup.
If you cannot update today
Cisco says no workaround fixes the flaw, but it describes a temporary mitigation: turn off secondary authentication on the VPN connection profiles, or, if the default profile does not use it, turn off the profile list shown at login. Turning off secondary authentication lowers VPN security, and with the list off staff must know which profile to use. Cisco asks you to assess the effect on your own setup first and treats this as temporary until you upgrade.
How to check
Ask your provider to confirm in writing which release the firewall runs now and that it matches the fixed version for your line under What we know. If your line was not listed, ask which fixed release they chose from Cisco’s advisory or Software Checker and why. Cisco’s Software Checker can also be run on the new release number to see whether this advisory still applies to it. Finally, have one remote worker connect to the VPN to confirm it works, and note the date of the update.
What we know
| Product | Cisco Secure Firewall ASA Software and Cisco Secure FTD Software |
|---|---|
| Vulnerabilities | CVE-2026-76418 |
| Fixed in | 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, 7.0.11, 7.2.13, 7.4.9, 7.6.7, 7.7.14, 10.0.3, 10.1.1 |
| Being exploited | Yes, confirmed by CISA |
| Listed by CISA | 29 October 2026 |
Sources
Educational content. Not a substitute for a qualified security audit or incident response advice for your specific environment.