Daily · Article 02 · 3 min read
- Security
Exploited Cisco VPN flaw can interrupt work before login succeeds
October 28 Cisco advisory · October 29 CISA addition · rechecked October 30 JST
Summary
CISA added the Cisco ASA/FTD VPN reload flaw to its exploited catalog on October 29. Exposure depends on affected software, reachable SSL remote-access VPN and secondary-authentication settings together. Verify the fix on the running device.
A dropped VPN connection can stop work for someone connecting to the office from home. Network-equipment maker Cisco disclosed a flaw where crafted requests to some firewall VPN services can unexpectedly reload the device. The US cybersecurity agency CISA added it to its exploited-vulnerability catalog on October 29.
Key facts
CVE-2026-76418 affects SSL remote-access VPN processing in Cisco Secure Firewall ASA and FTD software. An attacker can trigger a device reload without successfully logging in, causing denial of service: loss of normal access. Cisco’s advisory of October 28 at 19:15 GMT (October 29 at 04:15 JST) says it is aware of active exploitation and has released fixes. Cisco original
The CISA catalog release was at 04:09:34 JST on October 30. Read the affected scope as a combination of vulnerable software, reachable SSL remote-access VPN and secondary authentication in the relevant tunnel group. It does not cover every Cisco device or every VPN. CISA catalog

1. Why can a device reload before a password is accepted?
A VPN creates an encrypted connection between an outside PC and an organizational network. Before it decides whether login succeeds, the device must read the connection request and process the authentication setup. This flaw concerns that processing when secondary authentication is configured on a tunnel group, a collection of connection-profile settings.
%% From pre-login requests to interruption · Cisco CVE-2026-76418 conditions
flowchart TD
A["External VPN connection request"] --> B["All conditions:<br/>Affected version, reachable VPN<br/>Relevant secondary authentication"]
B --> C["Crafted request hits logic error<br/>Device reload interrupts access"]An ordinary request proceeds through authentication toward network access. A request matching the attack conditions can disrupt the device before successful authentication. The described harm is lost availability; this flaw alone does not establish data theft or server command execution.
The cat asks Q&A
- The researcher
Would a harder password prevent this interruption?
Pocket NotebookPassword length cannot fix a processing error reached before login. It also does not make secondary authentication inherently bad. The device administrator needs to assess affected settings and fixed software.
2. Hidden profile lists can leave an affected default
Cisco says not to check only whether the selectable tunnel-group list is hidden. If the default group, DefaultWEBVPNGroup, still uses secondary authentication, hiding the list can leave exposure. For FTD, examine the deployed device configuration as well as the policy in its management interface.
| Check location | Question |
|---|---|
| Running software | Is this an affected ASA or FTD release? |
| External connection path | Is the SSL remote-access VPN login service reachable? |
| Profile list and default group | Is relevant secondary authentication configured? |
- Check location
Running software
- Question
- Is this an affected ASA or FTD release?
- Check location
External connection path
- Question
- Is the SSL remote-access VPN login service reachable?
- Check location
Profile list and default group
- Question
- Is relevant secondary authentication configured?
An administrator can compare these settings through safe, read-only inspection. Sending attack requests to see whether a production device reloads is not an ordinary check.
The cat asks Q&A
- The researcher
What should I send the IT team?
Pocket NotebookGive CVE-2026-76418 and ask about the running ASA/FTD version, VPN reachability and secondary authentication, including the default group. The answer should say whether the deployed configuration was inspected. A screenshot of a hidden list is not enough evidence.
3. Verify a fix without weakening authentication
Cisco says there is no workaround that resolves the flaw and recommends fixed software. Some temporary mitigation in the advisory removes secondary authentication and can lower security; it is not presented here as an instruction for readers to copy.
| Example current series | First fix for this flaw | Full table |
|---|---|---|
| ASA 9.20 | 9.20.4.50 | Fixed Software in the Cisco original |
| FTD 7.4 | 7.4.9 | Fixed Software in the Cisco original |
- Example current series
ASA 9.20
- First fix for this flaw
- 9.20.4.50
- Full table
- Fixed Software in the Cisco original
- Example current series
FTD 7.4
- First fix for this flaw
- 7.4.9
- Full table
- Fixed Software in the Cisco original
These examples are neither every supported series nor today’s latest recommended releases. Administrators need the original’s full table, compatibility guidance and upgrade procedure for their devices. A completed download and fixed software actually running on a device are separate states.
The cat asks Q&A
- The researcher
What evidence helps establish service after the change?
Pocket NotebookAsk for the running software version, completion record and a normal VPN connection check. One successful connection alone does not demonstrate that the flaw was fixed. Use version evidence and normal operation together.
To close
The relevant check is on the VPN device
Running software and deployed settings address this flaw more directly than a user password change. Having the network operator establish both the official fix and ordinary connectivity keeps account protection distinct from service availability.
Sources
- Cisco originalsec.cloudapps.cisco.com
- CISA catalogcisa.gov