Cadenas à code posé sur un clavier
Home » News » Common Vulnerabilities and Exposures (CVE) » CVE-2026-76418: Cisco ASA and FTD SSL VPN flaw is exploited

CVE-2026-76418: Cisco ASA and FTD SSL VPN flaw is exploited

Mis à jour le

/


CVE-2026-76418 is a denial-of-service flaw affecting the remote access SSL VPN of Cisco Secure Firewall ASA and Secure Firewall Threat Defense (FTD) devices. Cisco published its advisory and fixes on October 28, 2026, after seeing active attacks in October, and CISA added it to its KEV catalog on October 29, with a November 1 deadline for US federal agencies. A remote attacker with no credentials can make the device reload and cut off remote access.

The flaw is rated 8.6 out of 10 on CVSS 3.1, according to Cisco’s official advisory. It sits in the same batch of additions as the critical GitLab flaw CVE-2026-97229, rated 10.0 and allowing unauthenticated code execution, as The Hacker News reported. Here is what is established, where sources differ and what to do.

Blue Ethernet network cable plugged into a device
A firewall’s remote access SSL VPN can be knocked offline by a single request

What does CVE-2026-76418 do to Cisco firewalls?

It lets an unauthenticated remote attacker send a crafted request to the SSL VPN login service and trigger an unexpected reload of the device, which is a denial of service. Cisco describes neither code execution nor data theft.

The cause is logic errors when secondary authentication is configured on a tunnel group, Cisco says. For SOC Prime, it is a null pointer dereference caused by an unchecked return value (CWE-690). The advisory rates the impact on confidentiality and integrity as none, and on availability as high. Cisco says its PSIRT became aware of active exploitation in October 2026, but according to BleepingComputer it gave no indicators of compromise and no detail about the attackers or targets.

Which products and configurations are affected by CVE-2026-76418?

Cisco Secure Firewall ASA and Secure FTD software, but only when three conditions are met: a vulnerable release, a reachable SSL VPN login service and secondary authentication configured in a tunnel group. A successful login is not needed to reach the faulty code.

Cisco says Cloud-delivered Firewall, cdFMC, Secure Access and Secure Firewall Management Center are not affected. You must check every tunnel group, including DefaultWEBVPNGroup, and not only the profiles shown on the login page. According to BleepingComputer, Shadowserver tracks more than 51,000 Cisco ASA SSL VPN devices exposed to the internet, without saying how many are vulnerable or already patched.

Which fixed versions should you install?

Install the first fixed release for your branch. For ASA: 9.16.4.104, 9.18.4.96, 9.20.4.50, 9.22.3.200, 9.23.1.48, and 9.24.1.27 or 9.24.10.1. For FTD: 7.0.11, 7.2.13, 7.4.9, 7.6.7, 7.7.14, 10.0.3 and 10.1.1, according to Cisco’s table.

Cisco’s Software Checker confirms the right release for your hardware, and FTD upgrades follow the Secure FMC upgrade guide. According to Tech Insider, version 7.4.8, fixed for a different flaw, does not contain this fix, which we could not cross-check with Cisco.

What do the sources say, and where do they differ?

They agree on the essentials: denial of service, fixes available, exploitation confirmed by Cisco. The gaps concern details worth knowing.

  • KEV listing date: Security Affairs gives October 28, while The Hacker News, Rescana and the CISA bulletin say the 29th. We use the 29th. That bulletin corrects an earlier message that wrongly listed a vulnerability, and it states no deadline, which The Hacker News and Security Affairs set at November 1.
  • Fixed versions: BleepingComputer, The Hacker News and Security Affairs do not list them, and Tech Insider notes that some outlets differ on at least one ASA build. We used Cisco’s table.
  • Workaround: Cisco writes that no workaround addresses the flaw, while offering a mitigation. Aviatrix presents two options without separating Cisco’s cases, and Tech Insider quotes CSO Online as saying only patches exist.
  • Start and scope of exploitation: Cisco says “in October 2026”, BleepingComputer and The Hacker News say “earlier in October”. The Hacker News adds that it is unclear whether it was limited to crashes. Aviatrix suggests a possible ArcaneDoor-style follow-up, without evidence.

Our analysis: what to take away from CVE-2026-76418

Our analysis: do not stop at the label “simple denial of service”. A remote access VPN that can be made to reload at will cuts off remote work, exploitation is confirmed and the US deadline of November 1 passed a week ago. If you are affected, patching is the priority.

The scope is bounded, though: without secondary authentication in a tunnel group, the vulnerable path is not reached. We see nothing linking this exploitation to the GitLab one; the two appear together only in the same catalog update. We also covered the Cisco Secure Email Gateway flaw CVE-2026-76519, another sign that edge devices remain favorite targets.

What to do about CVE-2026-76418

Upgrade to a fixed release, which Cisco strongly recommends. Until then, apply Cisco’s mitigation on the affected tunnel groups, after testing it in your own environment. Here is the order we suggest:

  1. Check your configuration: look for webvpn and secondary-authentication-server-group on every tunnel group, including DefaultWEBVPNGroup.
  2. Plan the upgrade to the fixed release for your branch, using Cisco’s Software Checker.
  3. Apply the mitigation meanwhile: if DefaultWEBVPNGroup does not use secondary authentication, no tunnel-group-list enable; otherwise no secondary-authentication-server-group, which lowers VPN security.
  4. Watch for unexpected reloads, advice from Rescana and not from Cisco, and restrict allowed source addresses on the VPN interface where you can.
  5. Update GitLab too if you self-host it, since its flaw CVE-2026-97229 is in the same catalog batch.

Frequently asked questions about CVE-2026-76418

What is CVE-2026-76418?

A denial-of-service flaw, rated 8.6 on CVSS 3.1, in the remote access SSL VPN of Cisco Secure Firewall ASA and Secure FTD. A crafted request makes the device reload, with no prior authentication.

Does CVE-2026-76418 let an attacker take control of the firewall?

Not according to Cisco, which describes only a reload and mentions neither code execution nor data theft. The impact is high on availability only.

Is my firewall vulnerable to CVE-2026-76418?

It is if it runs an unfixed release, exposes the SSL VPN login service and has secondary authentication configured in a tunnel group, including DefaultWEBVPNGroup.

Is there a fix for CVE-2026-76418?

Yes, Cisco published fixed releases on October 28, 2026 for ASA and FTD. Meanwhile, a mitigation is to disable secondary authentication or the group list, depending on your configuration.