Skip to content
Quantum Secure Labs
Cybersecurity News

Cisco fixes a zero-day in the SSL VPN of its ASA and FTD firewalls already used to knock them offline

Cisco has patched CVE-2026-76418, a zero-day flaw in the SSL VPN of its ASA and FTD firewalls that attackers are already exploiting to reboot them remotely without authenticating. It affects anyone with the VPN exposed…

By Quantum Secure Labs4 min read
Cortafuegos de red en un rack de servidores con cables conectados
In this article

Cisco has patched CVE-2026-76418, a zero-day flaw in the SSL VPN of its ASA and FTD firewalls that attackers are already exploiting to reboot them remotely without authenticating. It affects anyone with the VPN exposed to the internet and secondary authentication set on a tunnel group. Check your version today and update.

Key facts

  • CVE-2026-76418, CVSS 8.6: remote, unauthenticated denial of service in the remote access SSL VPN service of Cisco Secure Firewall ASA and Secure FTD. The device reloads unexpectedly (The Hacker News).
  • Cisco released patches on 29 October. Its PSIRT team learned of active exploitation in October but has shared no indicators of compromise and no details on who is attacking or whom.
  • CISA added the flaw to its Known Exploited Vulnerabilities (KEV) catalog on 29 October (CISA).
  • Shadowserver tracks more than 51,000 Cisco ASA devices with SSL VPN exposed online, without saying how many are already patched (BleepingComputer).
  • It is the second denial-of-service zero-day in these firewalls since August, after CVE-2026-20349.

Does it affect me if I use Cisco for remote work VPN?

If you use a Cisco ASA or Firepower (FTD) firewall for staff VPN or to link offices, it might. According to Cisco, the device is vulnerable when three conditions are met at once:

  1. It runs an affected version.
  2. The SSL VPN login service is reachable.
  3. Secondary authentication is configured at the tunnel group level.

The root cause is logic errors in that configuration. A crafted request when connecting to the SSL VPN is enough, and the attacker doesn't need a valid login to reach the vulnerable code path. If your IT provider manages the device, this question is for them. If you don't use Cisco, you're not affected.

Which version do I need?

Fixed ASA versions: 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.

Fixed FTD versions: 7.0.11, 7.2.13, 7.4.9, 7.6.7, 7.7.14, 10.0.3 and 10.1.1.

If your device isn't on one of these versions or later within its branch, you need to update.

What if I can't patch today?

Cisco offers a temporary mitigation: disable secondary authentication on the default tunnel group (DefaultWEBVPNGroup) and on any user-configured group. If DefaultWEBVPNGroup doesn't use secondary authentication, the alternative is to disable the tunnel group list.

This has a cost: it weakens VPN access security. And, as BleepingComputer notes, Cisco offers no workaround that fully fixes the issue. It's a stopgap, not a solution.

What to do today

  1. Find out whether you have Cisco ASA or FTD. If you don't know, ask your IT provider today, in writing.
  2. Get the exact installed version and compare it with the fixed ones above.
  3. Confirm whether secondary authentication is configured on any tunnel group.
  4. If the version is vulnerable, schedule the update as soon as possible, even if it means a short outage after hours.
  5. If you can't update today, apply Cisco's mitigation and record that it's temporary.
  6. Check that the VPN interface isn't exposed to the internet without need.
  7. If the firewall has rebooted with no explanation, treat it as suspicious and alert your provider or INCIBE-CERT, which published a notice on multiple vulnerabilities in Cisco products on 29 October.

What it means for a small business

From what's been described, this flaw isn't for stealing data. It's for knocking the device over. But in a small business the firewall is often the only door: if it reboots again and again, remote staff lose the VPN and the office may lose internet access. For a 30-person company working remotely, that's a lost day.

What worries us most is the pattern. This is the second zero-day of this kind in these devices since August. If your firewall only gets updated when someone remembers, that's the real problem, not this specific CVE.

Our advice: treat the firewall as a critical asset with its own patch schedule. Ask your provider for a clear commitment on how quickly they patch exploited flaws and to tell you when they do. If nobody is watching it, this is exactly the kind of task worth outsourcing carefully; we cover it in our cybersecurity service.

Frequently asked questions

Can attackers steal data with this flaw?

Cisco describes it as denial of service: the device reloads unexpectedly. The main risk is losing your VPN and network.

Is the mitigation enough?

No. It's temporary, it weakens access security and Cisco offers no workaround that fully fixes the issue. You need to update.

How do I know if I've already been hit?

Cisco hasn't published indicators of compromise. The practical signal is firewall reboots nobody can explain.

Sources

Worried about a threat like this one?

We review your exposure and show you how to protect yourself.

See our cybersecurity service

Cybersecurity News

CISA confirms PolyShell flaw in Adobe Commerce and Magento is exploited as hundreds of stores are hit

CISA has added CVE-2026-48356 (PolyShell), a critical Adobe Commerce and Magento vulnerability, to its catalogue of exploited flaws, and attackers are already using it to infect online stores. If you sell on Magento 2…

Cybersecurity News

Tailscale 1.104.4 fixes Tailworm SSH flaws that let a compromised device get root on other servers

Tailscale has released version 1.104.4 to fix the flaws in its SSH server known as Tailworm, which let a compromised device gain root on other servers in the network. It affects anyone running Tailscale SSH on Linux or…

Cybersecurity News

Gheist: stolen GitHub tokens pull secrets from private repositories through Actions logs

An automated campaign called Gheist uses stolen GitHub tokens to plant workflows that print repository secrets, including private and GitHub Enterprise ones, into Actions logs. If your team uses GitHub with CI/CD…

Want to apply these ideas to your business?

Tell us about your case and we'll show you how to apply these strategies to your project.