Skip to content
Reachability Analysis

CVE-2026-76418: Cisco Secure Firewall ASA and FTD, is it exploitable where you run it

Code called: openReached: yesControl in front: noExploitation known: yesWalk it through the four questions

What the flaw is

CVE-2026-76418 is a flaw in the Remote Access SSL VPN service of Cisco Secure Firewall ASA Software and Secure Firewall Threat Defense (FTD) Software. Cisco attributes it to logic errors when secondary authentication is configured on a tunnel group; CISA labels the weakness an unchecked return value leading to a NULL pointer dereference (CWE-690).

An unauthenticated attacker on the network can send a crafted request to the SSL VPN login service and make the device reload unexpectedly. The result is denial of service: VPN users lose their sessions and the firewall is offline until it restarts. Cisco says a successful VPN login is not needed to reach the affected code. Cisco rates it 8.6 (CVSS 3.1 base score; scope changed, availability impact high, no confidentiality or integrity impact).

Are you exposed: each condition and how to check it

Condition for exposureHow to check it on your system
the release is earlier than the first fixed release for its train, with Remote Access SSL VPN enabled on an interface the attacker can reachVersion: on ASA run show version and read the Software Version. On FTD run show version in the FTD CLI, or open Devices > Device Management in Secure FMC (or Device > Summary in FDM). Compare with the versions table, or enter the release in the Cisco Software Checker. SSL VPN enabled: on ASA run show running-config webvpn and look for enable <interface_name>. On FTD, remote access VPN is enabled from Devices > VPN > Remote Access in Secure FMC or from Remote Access VPN in FDM, so review the deployed policy there and the resulting running configuration. Reach: take the interface named in the enable line, check its IP address and the access rules or upstream firewall that expose it, and test the login page from an untrusted network. An internet-facing interface is the high-risk case.
a tunnel group in scope uses secondary authenticationRun show running-config tunnel-group and search for secondary-authentication-server-group in every tunnel group, including DefaultWEBVPNGroup. A group is in scope when tunnel-group-list enable is set (check all groups, not only those shown on the login page) or, when it is not set or was removed with no tunnel-group-list enable, when it is the default group DefaultWEBVPNGroup; disabling the list does not remove exposure when that default group uses secondary authentication.

Affected and fixed versions

Cisco confirms these products are not affected: Cloud-delivered Firewall, cdFMC, Secure Access and Secure FMC Software. The Cisco Software Checker returns the first fixed release for a given running release. Cisco validates only the affected and fixed release information in the advisory.
Product and trainAffectedFirst fixed release
ASA 9.16 and earlierEarlier than 9.16.4.1049.16.4.104
ASA 9.18Earlier than 9.18.4.969.18.4.96
ASA 9.20Earlier than 9.20.4.509.20.4.50
ASA 9.22Earlier than 9.22.3.2009.22.3.200
ASA 9.23Earlier than 9.23.1.489.23.1.48
ASA 9.24Earlier than the fixed release for the running minor train9.24.1.27 and 9.24.10.1 (Cisco lists both in the 9.24 row without naming the train each serves; the Software Checker returns the one for your running release)
FTD 7.0 and earlierEarlier than 7.0.117.0.11
FTD 7.2Earlier than 7.2.137.2.13
FTD 7.4Earlier than 7.4.97.4.9
FTD 7.6Earlier than 7.6.77.6.7
FTD 7.7Earlier than 7.7.147.7.14
FTD 10.0Earlier than 10.0.310.0.3
FTD 10.1Earlier than 10.1.110.1.1

If the fix cannot go in yet

  • Upgrade to the first fixed release for your train. Cisco strongly recommends this and says no workaround addresses the flaw; the two cases below are a temporary mitigation only.
  • Mitigation, Case 1: if DefaultWEBVPNGroup does not use secondary authentication, disable the tunnel group list with no tunnel-group-list enable in WebVPN configuration mode. Cost: users can no longer pick a connection profile from a list on the login page and must know the right profile name.
  • Mitigation, Case 2: if DefaultWEBVPNGroup uses secondary authentication, remove it with no secondary-authentication-server-group. Cost: the remote access VPN security posture drops, since users are no longer asked for the second credential. Cisco says the mitigation was proven in a test environment, tells customers to check it in their own environment first, and prefers the upgrade.
  • The aim is that no tunnel group in scope uses secondary authentication. In Case 1 the group list is off, so the only group in scope is DefaultWEBVPNGroup, which has none. In Case 2 secondary authentication is removed from DefaultWEBVPNGroup, and any user-configured group in an enabled group list must lose it too.

What to look for

  • After a suspected attack, show crashinfo on the ASA or FTD lists the crash or traceback record that an unexpected reload leaves, and show version shows the uptime since the last reload. A reload with no planned change, repeated while the SSL VPN is reachable, matches the symptom.
  • Cisco publishes no log strings, syslog message IDs or indicator addresses for this flaw. For FTD, collect a troubleshoot file from Secure FMC or FDM before sharing crash data with Cisco TAC.

The earliest dated mark of exploitation is CISA's, on 28 Oct 2026, the day of disclosure; exploitation may have begun earlier.

Exploitation reported so far

Cisco states that in October 2026 its PSIRT became aware of active exploitation of this vulnerability, without naming a day, and recommends upgrading. The earliest dated report is CISA's SSVC entry in NVD, stamped 28 Oct 2026, the day of the advisory, with exploitation active and automatable yes. CISA added the CVE to KEV on 29 Oct 2026.

No attacker names, campaign details or indicators are published. KEV lists ransomware campaign use as Unknown.

Why static reachability settles it

Exposure needs a vulnerable release, SSL VPN enabled on an interface and secondary authentication in a tunnel group in scope. The version and both settings show in the running configuration, so a static check of the config settles those three exactly. Whether the login service is reachable depends on the network path, so test it from an untrusted network. A device that matches all of these is exposed to a no-login attack that is already being used. See static reachability for what the method proves and misses.

Sources

  1. CVE-2026-76418: NVD record, read 19 Nov 2026
  2. CVE-2026-76418: CISA KEV entry (feed version 2026.11.18), read 19 Nov 2026
  3. CVE-2026-76418: Cisco security advisory cisco-sa-asaftd-tunnel-dos-s6mgkb75 (vulnerable configuration, mitigation, fixed releases), read 19 Nov 2026

Last reviewed 19 Nov 2026.