Deception Check

RESPONSE NOTES / REMOTE ACCESS / OCTOBER 30, 2026

A Cisco VPN flaw can restart the firewall before login.

If that VPN carries your maintenance access, a firewall outage can become a support outage. Start with the configuration, match the fix to the running software, and keep enough evidence to explain an unexpected restart.

By Deception Check / CVE-2026-76418 / Sources checked October 30 / Includes a response worksheet and native-log hunt starters

Who should check: teams running Cisco Secure Firewall ASA or FTD with SSL remote-access VPN and secondary authentication in the tunnel-group scope described below. The flaw is being exploited. A successful VPN login is not required to reach the affected processing path.

The login service can fail before it lets anyone in

A remote-access VPN is an encrypted connection that lets approved people reach an organization's network from elsewhere. Cisco ASA and FTD firewalls can provide that service as well as filter network traffic.

In Cisco's advisory for CVE-2026-76418, a crafted request to the SSL VPN service can cause an affected device to reload. Reload means the device restarts. The trigger involves secondary authentication, a second authentication step configured on a VPN connection profile, called a tunnel group. It does not require the sender to complete a VPN login.

Cisco rates the flaw High, 8.6 under the Common Vulnerability Scoring System and confirms active exploitation. The disclosed impact is denial of service: interruption of availability. If this firewall provides remote engineering or vendor access, review which support tasks depend on it. The operational consequence depends on how your network and failover are built.

8.6VENDOR CVSS / HIGH
No loginNEEDED TO REACH THE FLAW
Fix by branchNO SINGLE VERSION FLOOR

HOW THE FAILURE HAPPENS / ADVISORY-DERIVED EXPLANATION

01 / REACH THE VPN

A crafted request reaches the login service

The sender does not need a successful VPN login.

SSL remote-access VPN is reachable
02 / HIT THE AFFECTED PATH

Secondary-authentication processing fails

A vulnerable release processes the affected tunnel-group configuration.

CWE-690 / NULL pointer: invalid memory access
03 / LOSE AVAILABILITY

The device can restart

Access through the affected device can be interrupted. Check your failover and recovery behavior.

Denial of service / availability impact
This diagram explains Cisco's disclosed failure. It does not show an attacker passing through the firewall or taking control of a plant. Source: Cisco advisory and CNA.

Three decisions to assign now

01 / FIREWALL OWNER

Check the actual exposure

Confirm the running release, VPN service reachability, and the relevant secondary-authentication configuration. Include the default profile.

02 / CHANGE OWNER

Install a supported fix

Use the fixed release for your branch and platform. After maintenance, record the version actually running on each applicable member.

03 / RESPONSE OWNER

Keep the restart evidence

Preserve externally collected logs, crash information, and the change timeline. Establish who responds if VPN access disappears.

CONFIGURATION CHECK / GIVE THIS TO THE FIREWALL OWNER

Check the default VPN profile, too.

First establish the product, running release, and whether the SSL remote-access VPN service is enabled and reachable. Then follow the group-list branch below.

Is the VPN connection-profile list enabled?

tunnel-group-list enable
YES / LIST ENABLED

Inspect every tunnel group

  • Include DefaultWEBVPNGroup.
  • Include profiles not shown in the login-page list.
  • Look for secondary-authentication-server-group.
NO / LIST ABSENT OR REMOVED

Inspect the default tunnel group

  • Check DefaultWEBVPNGroup for secondary authentication.
  • Removing the list alone does not remove exposure when the default group still uses it.
Secondary authentication present in the relevant scope? Treat the configuration as a potential exposure until you match the running software to Cisco's fix table. If the configuration or version is unknown, assign an owner to verify it rather than marking it clear.
On FTD, review both the deployed remote-access VPN policy and resulting running configuration through FMC or FDM. This is a configuration review, not a test exploit. Source: Cisco advisory.

A newer version number does not guarantee a fix

Software branches receive different maintenance releases. An ASA build on the 9.20 branch is not cleared by a minimum listed for 9.16. Use the Cisco Software Checker and the current advisory for your exact installation. The table preserves Cisco's first-fixed mappings as checked on October 30.

ASA software

Running branchFirst fixed release
9.16 and earlier9.16.4.104
9.189.18.4.96
9.209.20.4.50
9.229.22.3.200
9.239.23.1.48
9.249.24.1.27 or 9.24.10.1

FTD software

Running branchFirst fixed release
7.0 and earlier7.0.11
7.27.2.13
7.47.4.9
7.67.6.7
7.77.7.14
10.010.0.3
10.110.1.1

A first-fixed entry is not a blanket recommendation to move an old platform to that build. Check hardware support, upgrade path, and other applicable advisories. Cisco lists both 9.24 fix entries; confirm the appropriate release for your deployment.

Temporary mitigation needs a configuration decision

Cisco lists no complete workaround and recommends upgrading. Its conditional mitigations depend on whether the default group uses secondary authentication: one case disables the connection-profile list; the other removes secondary authentication and lowers VPN security. Have the firewall and identity owners evaluate Cisco's full instructions and their operational impact. Do not turn this into a general instruction to switch off MFA.

PUBLIC TIMELINE / CALENDAR DATES, NOT MEASURED ATTACK DURATION

DISCLOSUREOctober 28

Cisco publishes the advisory and fixed-release guidance.

KNOWN EXPLOITATION CATALOGOctober 29

CISA adds the vulnerability to KEV.

FEDERAL DUE DATENovember 1

The catalog gives this remediation date for covered federal agencies under applicable CISA direction.

Other organizations can use known exploitation to prioritize action; the federal deadline is not a universal private-sector legal deadline. Sources: Cisco advisory and CISA's official catalog.

An unexplained restart is a reason to investigate

A restart alone does not identify the cause. Planned maintenance, power problems, software faults, and an attack can look similar from a user's disconnected VPN session. Compare the device record with a separately retained timeline before deciding which explanation fits.

  1. Keep what already exists.

    Preserve external syslog around the event, time zone and clock information, monitoring alerts, VPN session/disconnect records, and crash artifacts through approved Cisco support procedures. Protect these records as operational data; keep raw configurations and credentials out of public tickets.

  2. Check the change and resilience story.

    Was a reload approved? Did power or monitoring fail at the same time? What happened on the peer appliance? Check actual failover behavior rather than assuming all access survived or all sessions failed.

  3. Correlate the VPN activity.

    Where retained, compare authentication events and relevant network activity before the restart. Encrypted traffic may not expose request contents to a network sensor. A source address or failed login is an investigation lead, not an exploit verdict.

  4. Escalate unexplained events.

    Give the response owner and Cisco TAC the running version, relevant configuration scope, exact times, restart/crash evidence, and change history. Preserve evidence before avoidable resets or cleanup. Remediating this DoS does not rule out unrelated compromise.

NETWORK TEAM RECEIPT

What is running?

Device or pair, software branch, active version after maintenance, relevant VPN configuration, change reference, and recovery owner.

RESPONSE TEAM RECEIPT

What explains the event?

Restart time, collector/source identity, retained crash information, nearby session events, and an explicit next action.

Download the two-page response worksheetOpen the readable worksheet

Find startup records in the logs you already collect

There is enough public documentation to build useful restart-investigation searches. There is not enough in the sources reviewed to identify this crafted request reliably. The Sigma rule and four native searches below use original Cisco appliance messages, without a Deception Check schema or an endpoint agent on the firewall.

What a result means: a documented startup message was retained. It is a place to start an investigation, not a CVE detection verdict. Planned updates, power events, and unrelated faults can match. An empty result can reflect missing telemetry.

Cisco message IDWhat it recordsHow to use it
199005Startup beginningFind candidate boot activity in the incident window.
199002Startup completionCompare with uptime and other records. Begin and completion can be one boot.
199001User-initiated reloadContext only. Do not infer an attack from its absence or automatically exclude a candidate when it is present.

Have your administrator confirm that appliance messages, including informational severity, are actually forwarded and retained. Verify device identity and timestamps against inventory; a collector name is not necessarily the firewall. Each platform needs its normal ingestion, retention, and search entitlement.

Without a SIEM: start with the device and your existing central log collector. Cisco's unexpected-reload guide documents application-uptime checks with show version on ASA and show version system on FTD. Use the platform-specific guidance to collect support evidence. Do not restart production merely to test collection.

Sigma / ordinary Cisco appliance syslog

This rule uses the actual telemetry vendor, product: cisco, and standard full-event keyword matching over retained ASA/FTD syslog. Deception Check appears as the author. No custom service, normalized fields, or schema.md is required.

Use your normal source selection and a Sigma backend that supports raw-message keyword searches. The rule surfaces startup records for investigation; routine restarts are expected matches.

title: Cisco ASA or FTD Startup Event
id: df77e550-de30-4ea5-8d52-1de0dbf6f569
status: experimental
description: >-
    Finds documented Cisco ASA or FTD startup messages in original appliance syslog. Use these
    events to investigate restarts; they do not identify the cause or establish exploitation
    of CVE-2026-76418.
references:
    - https://www.cisco.com/c/en/us/td/docs/security/asa/syslog/asa-syslog/syslog-messages-101001-to-199021.html
    - https://www.cisco.com/c/en/us/td/docs/security/firepower/Syslogs/fptd_syslog_guide/syslogs1.html
author: Deception Check
date: '2026-10-30'
logsource:
    product: cisco
    definition: >-
        Original Cisco ASA or FTD appliance syslog with the ASA/FTD message prefix retained.
        Select the actual firewall source and use a backend that supports full-event keyword
        matching.
detection:
    keywords:
        - '*%ASA-0-199002:*'
        - '*%ASA-0-199005:*'
        - '*%ASA-1-199002:*'
        - '*%ASA-1-199005:*'
        - '*%ASA-2-199002:*'
        - '*%ASA-2-199005:*'
        - '*%ASA-3-199002:*'
        - '*%ASA-3-199005:*'
        - '*%ASA-4-199002:*'
        - '*%ASA-4-199005:*'
        - '*%ASA-5-199002:*'
        - '*%ASA-5-199005:*'
        - '*%ASA-6-199002:*'
        - '*%ASA-6-199005:*'
        - '*%ASA-7-199002:*'
        - '*%ASA-7-199005:*'
        - '*%FTD-0-199002:*'
        - '*%FTD-0-199005:*'
        - '*%FTD-1-199002:*'
        - '*%FTD-1-199005:*'
        - '*%FTD-2-199002:*'
        - '*%FTD-2-199005:*'
        - '*%FTD-3-199002:*'
        - '*%FTD-3-199005:*'
        - '*%FTD-4-199002:*'
        - '*%FTD-4-199005:*'
        - '*%FTD-5-199002:*'
        - '*%FTD-5-199005:*'
        - '*%FTD-6-199002:*'
        - '*%FTD-6-199005:*'
        - '*%FTD-7-199002:*'
        - '*%FTD-7-199005:*'
    condition: keywords
falsepositives:
    - Planned updates, approved restarts, power events, and unrelated software faults.
    - Forwarded or quoted startup messages from outside the intended appliance source.
level: informational

Download the Sigma rule / Sigma keyword and wildcard specification / Source setup and compatibility notes

Sigma keyword matching is case-insensitive; the native searches below retain Cisco's documented uppercase prefixes. Schema checks, pySigma parsing, local matching fixtures, and one Splunk conversion were checked. No backend or tenant execution is claimed.

Splunk

Original Cisco syslog in your chosen index; documented cisco:asa or cisco:ftd source types. No CIM or Enterprise Security model required.

index=YOUR_CISCO_SYSLOG_INDEX (sourcetype="cisco:asa" OR sourcetype="cisco:ftd") earliest=-7d
| regex _raw="%(ASA|FTD)-[0-7]-(199002|199005):"
| table _time host source sourcetype _raw

Download exact query / Cisco syslog source setup

Microsoft Sentinel

Cisco appliance syslog in the native Syslog table via your configured forwarder and data collection rule. CEF-only CommonSecurityLog ingestion needs a separate mapping.

Syslog
| where TimeGenerated >= ago(7d)
| where SyslogMessage matches regex @"%(ASA|FTD)-[0-7]-(199002|199005):"
| project TimeGenerated, EventTime, HostName, HostIP, Computer, CollectorHostName, SyslogMessage

Download exact query / Syslog table and field definitions

Sumo Logic

Original Cisco syslog in your selected source category. Choose the incident window in the search UI.

_sourceCategory="YOUR_CISCO_SYSLOG_CATEGORY"
| where _raw matches /(?s).*%(ASA|FTD)-[0-7]-(199002|199005):.*/

Download exact query / Matches operator and regex syntax

CrowdStrike Falcon LogScale

Imported Cisco appliance logs in your selected repository/view. This is not Falcon endpoint EDR telemetry. Choose the incident window in the search UI.

@rawstring = /%(ASA|FTD)-[0-7]-(199002|199005):/

Download exact query / Field-specific regex query syntax

Validation: the exact message predicates were checked against positive, negative, and missing-data fixtures. These are read-only investigation starters, not production alert rules. Platform query execution, real-appliance testing, and customer-tenant validation were not performed. Run an administrator-reviewed sample search and verify source selection, device identity, and retained messages before operational use.

This pack leads with a standard Sigma keyword rule and retains the native searches for direct use. Ordinary source selection and raw-message keyword support are required; no new normalization schema is introduced. An actual Splunk conversion was inspected, without claiming backend execution or identical free-text and regex behavior. A payload or packet signature, YARA rule, or workstation-EDR search would need different evidence; none is presented as exploit coverage here.

Message definitions: ASA startup messages / FTD startup messages. Examples in validation fixtures are synthetic documented formats, not captured attacks.

Sources and scope

This response note explains the vendor-disclosed issue and documented appliance-log symptoms. It reports no first-party capture of this CVE and does not join it to another campaign. No exploit was run. Updates and device-specific decisions should use the current Cisco guidance.