Cisco ASA and FTD SSL VPN vulnerability CVE-2026-76418 is under active exploitation, and a new October 29, 2026 government warning urges administrators to update affected firewalls. Cisco disclosed the high-severity issue on October 28, and the Canadian Centre for Cyber Security confirmed on October 29 that CISA added it to the Known Exploited Vulnerabilities catalog. Businesses using Cisco firewalls for remote employee access should check their exposure promptly.
What happened: an actively exploited Cisco SSL VPN flaw
Cisco published advisory cisco-sa-asaftd-tunnel-dos-s6mgkb75 on October 28. It describes a flaw in the remote access SSL VPN service of Cisco Secure Firewall Adaptive Security Appliance (ASA) and Secure Firewall Threat Defense (FTD) software. The vulnerability is tracked as CVE-2026-76418 and carries a CVSS v3.1 score of 8.6, classified as high severity.
Cisco says a remote attacker without a valid login can send a specially formed request during an SSL VPN connection attempt and cause a vulnerable firewall to reload. This is a denial-of-service risk, meaning connectivity and remote access can be interrupted. The advisory does not describe this flaw as allowing remote code execution or data theft.
What is confirmed as of October 30
Cisco’s Product Security Incident Response Team says it became aware of active exploitation during October 2026. The Canadian Centre for Cyber Security updated its advisory AV26-1102 on October 29 to report that the U.S. Cybersecurity and Infrastructure Security Agency had added CVE-2026-76418 to its Known Exploited Vulnerabilities catalog. NHS England also published an October 29 warning advising affected organizations to apply the relevant update.
The confirmed issue is availability disruption from unexpected device reloads. Cisco has not publicly identified the attackers, affected organizations, the number of incidents, or evidence of data theft attributable to this vulnerability in the cited advisory. Those details should not be assumed.
Which Cisco firewalls are affected?
Exposure requires a vulnerable ASA or FTD software release, a reachable SSL remote access VPN login service, and secondary authentication configured in an affected tunnel group. Cisco specifically directs administrators to examine the default tunnel group, DefaultWEBVPNGroup, as well as user-defined groups. A successful VPN login is not required to reach the vulnerable code path.
Cisco lists the following first fixed versions for the affected ASA release branches: 9.16.4.104, 9.18.4.96, 9.20.4.50, 9.22.3.200, 9.23.1.48, 9.24.1.27, and 9.24.10.1. For FTD, the first fixed versions are 7.0.11, 7.2.13, 7.4.9, 7.6.7, 7.7.14, 10.0.3, and 10.1.1. Administrators must match the correct fix to their installed software train and supported upgrade path.
Cisco says Cloud-delivered Firewall, Cloud-delivered Firewall Management Center, Secure Access, and Secure Firewall Management Center software are not affected by this particular vulnerability. That does not mean these products are free of unrelated security issues.
Why this matters to small businesses
Firewalls and VPN gateways often support remote work, vendor access, and business-critical connectivity. If a firewall repeatedly reloads, employees may lose remote access and dependent services may be interrupted. Organizations with a single VPN gateway may have fewer options for maintaining operations during an outage.
Small businesses using a managed IT provider should ask whether their remote access service runs on Cisco ASA or FTD and whether the affected configuration is present. A business does not need to manage the firewall itself to experience the consequences of an outage.
Practical defensive actions
1. Confirm the product, version, and VPN configuration
Inventory internet-facing Cisco ASA and FTD appliances and verify whether SSL remote access VPN is enabled. Review tunnel-group settings, including secondary authentication on the default group. Use Cisco’s official advisory and Software Checker to determine whether the installed release is affected.
2. Apply the fixed Cisco release
Prioritize affected remote access gateways and schedule a vendor-supported upgrade as soon as possible. Back up configurations, review compatibility, prepare a rollback plan, and validate VPN connectivity after maintenance. Cisco recommends upgrading to fixed software.
3. Evaluate temporary mitigations carefully
Cisco states that there is no workaround that fully addresses the vulnerability, but it documents temporary configuration mitigations involving the tunnel-group list or secondary authentication. Disabling secondary authentication can weaken VPN security, so organizations should not make this change without evaluating the impact and following Cisco’s precise guidance. Patching is the preferred remedy.
4. Investigate unexpected firewall reloads
Review device uptime, reload reasons, system logs, VPN availability alerts, and recent configuration changes. An unexpected restart is a reason to investigate, not by itself proof that this vulnerability was exploited. Preserve relevant logs and engage the firewall vendor or incident-response provider if suspicious activity is identified.
5. Plan for remote access interruptions
Document how staff and administrators can communicate during a VPN outage. Verify backup access arrangements and ensure emergency changes can be approved without relying entirely on the affected remote access service.
What remains unverified
The public advisories cited here do not establish a victim count, attacker identity, data exfiltration, or ransomware use tied to CVE-2026-76418. They do establish active exploitation and available vendor fixes. Businesses should treat the issue as an urgent availability risk while avoiding assumptions about compromise.