Cisco ASA and FTD CVE-2026-76418: SSL VPN reload flaw and fixed releases

Venus Yazılım5 min read

Unauthenticated attackers can reload Cisco ASA and FTD devices through SSL VPN when secondary authentication is set. It is being exploited. Check and upgrade.

If you use a Cisco ASA or FTD device for remote access VPN, an unexpected reload means a service outage for your remote users. This article covers a flaw in the SSL VPN service of these devices, which is being exploited in the wild.

Short answer: CVE-2026-76418 is a denial-of-service (DoS) flaw in the Remote Access SSL VPN service of Cisco Secure Firewall ASA and Cisco Secure FTD software. When secondary authentication is configured, an unauthenticated remote attacker can make the device reload. The CVSS 3.1 score is 8.6. CISA added the flaw to the KEV catalog on October 29, 2026. The fixed release is the first fixed release listed in the table below for your release line.

At a glance

Field Detail
CVE CVE-2026-76418 (Cisco Bug ID: CSCwx26625)
CVSS 8.6, High (v3.1, Cisco and NVD)
Flaw type Denial of service (DoS); unchecked return value leading to a NULL pointer dereference (CWE-690)
Authentication Not required (AV:N, PR:N, UI:N)
Active exploitation Yes. Cisco says it became aware of active exploitation in October 2026
CISA KEV added October 29, 2026
Fixed releases See the table below

What happened?

The flaw is in the Remote Access SSL VPN service. Cisco says it results from logic errors when secondary authentication is configured on a tunnel group. An attacker can send a crafted request to the SSL VPN login service and make the device reload.

A denial of service makes a system unavailable. In this case, the attacker cannot read or change data according to the CVSS vector (confidentiality and integrity impact: none). The device reloads and VPN sessions drop.

Cisco became aware of active exploitation in October 2026. The sources do not say when the attacks started, who carried them out, or how large they were.

Who is affected?

The device is affected when all three conditions below are true:

  1. SSL Remote Access VPN is enabled. The running configuration contains webvpn with enable on an interface.
  2. The SSL VPN login service is reachable.
  3. secondary-authentication-server-group is set on any tunnel group, including DefaultWEBVPNGroup.

If these conditions are met and your release is in the affected range, patch the device. Cisco says a successful VPN login is not needed to reach the affected code path.

According to Cisco, these products are not affected by this advisory: Cloud-delivered Firewall (CDFW), cdFMC, Secure Access (CSA), and Secure FMC Software.

What should you do?

  1. Check your configuration. On ASA, run:
show running-config | include secondary-authentication-server-group

On FTD, the setting is in FMC under Devices > VPN > Remote Access, or in FDM under Remote Access VPN.

  1. Check your software version. On ASA, run:
show version

Compare the result with the table below, or use the Cisco Software Checker, which lists the Cisco security advisories that apply to a specific release.

  1. Upgrade to the first fixed release. Cisco strongly recommends upgrading to a fixed release.
Product Release group First fixed release
ASA 9.16 and earlier 9.16.4.104
ASA 9.18 9.18.4.96
ASA 9.20 9.20.4.50
ASA 9.22 9.22.3.200
ASA 9.23 9.23.1.48
ASA 9.24 9.24.1.27, 9.24.10.1
FTD 7.0 and earlier 7.0.11
FTD 7.2 7.2.13
FTD 7.4 7.4.9
FTD 7.6 7.6.7
FTD 7.7 7.7.14
FTD 10.0 10.0.3
FTD 10.1 10.1.1

The table comes from the Cisco advisory and matches The Hacker News summary. The NVD record’s range for 7.6 includes 7.6.7, while Cisco lists 7.6.7 as the first fixed release. Verify your 7.6 release with the Cisco Software Checker before you rely on this row.

  1. If you cannot upgrade right away, use Cisco’s mitigation. Which step applies depends on whether DefaultWEBVPNGroup uses secondary authentication:
    • If DefaultWEBVPNGroup does not use secondary authentication, run no tunnel-group-list enable in WebVPN configuration mode. Users then need to know the correct connection profile name.
    • If DefaultWEBVPNGroup uses secondary authentication, no secondary-authentication-server-group removes it. Cisco notes that this lowers the VPN security posture, so treat it as a temporary step only.

Have I been hit?

Neither the Cisco advisory nor The Hacker News article lists indicators of compromise (IoCs) for this CVE. The checks below are general recommendations, not vendor-specific indicators.

  • Review unexpected reloads in your logs. Run show logging and look for reload events and VPN login attempts around the same time.
  • Check for an unusual rise in SSL VPN login attempts.
  • Read reloads, user reports, and logs together.

Frequently asked questions

Am I affected if I do not use remote access VPN?

No. The flaw requires the Remote Access SSL VPN service to be enabled and secondary authentication to be configured. Still, check your configuration with the command above.

What if I do not use secondary authentication?

According to the advisory, the flaw needs that configuration to be triggered. If your release is in the affected range, plan the upgrade anyway.

My device reloaded unexpectedly. Is this an attack?

It could be, but we cannot say so with certainty. The sources list no IoCs for this CVE. Compare the reload logs with your VPN login records.

What does the Cisco Software Checker do?

It takes a software release and lists the Cisco security advisories that affect it, along with the first fixed release. It is most useful for border cases in the table.

If you want help tracking patches for firewalls and VPN appliances, take a look at our server management service.

Sources

More notes

  1. 4 min read

    Google Brotli CVE-2026-111497: memory overflow in Node.js and Brotli libraries

    A memory overflow in the Brotli decoder (CVE-2026-111497) can lead to code execution without logging in. Update Node.js and Brotli.

  2. 4 min read

    GitLab CVE-2026-97229: unauthenticated remote code execution, CVSS 10.0

    CVE-2026-97229 in GitLab CE and EE (CVSS 10.0) can allow code execution without login under certain conditions. Upgrade to 19.2.8, 19.3.5, or 19.4.2.

Let’s reserve a slot in the rack.

Describe your project in a few steps and we’ll prepare a written proposal with scope, timeline and an infrastructure plan.

Request a quoteor write directly: email address