← Back to CVE intelligence
CVE intelligence

CVE-2026-20154

Vulnerability intelligence

Published Sep 16, 2026Sources checked Nov 10, 2026
8.6HIGHCVSS out of 10
What this means

Review the available evidence

CVE-2026-20154 and is rated High severity with a CVSS score of 8.6. It is not in the current CISA KEV record we collected. That does not prove exploitation has not occurred.

What to do next

Remediation and response

Cisco Security Advisories guidance

Vendor revision: Sep 18, 2026

Cisco has released software updates that address this vulnerability.

Cisco Security Advisories guidance

Vendor revision: Sep 16, 2026

To remediate these vulnerabilities, Cisco strongly recommends that customers upgrade to the fixed software that is indicated in the advisories.

CISA KEVNot listedBased on the latest collected catalog
EPSS0.6%Estimated 30-day exploitation probability
Ransomware useNot markedCISA KEV ransomware field
Threat actors0Source-linked actor relationships
Overview

What is CVE-2026-20154?

A vulnerability in the system rate-limiting process for syslog message 419002 of Cisco Secure Firewall Adaptive Security Appliance (ASA) Software and Cisco Secure Firewall Threat Defense (FTD) Software could allow an unauthenticated, remote attacker to cause high CPU utilization on an affected device, resulting in a denial of service (DoS) condition.

This vulnerability is due to improper rate limiting for syslog message 419002. An attacker could exploit this vulnerability by sending a flood of TCP synchronization (SYN) packets to an affected device.

A successful exploit could allow the attacker to cause high CPU utilization, resulting in performance degradation.

Source: NVD

Official advisory

Configuration and update guidance

Cisco Security Advisories · Updated Sep 18, 2026

Affected products and configuration

This vulnerability affects Cisco devices if they are running a vulnerable release of Cisco Secure Firewall ASA Software or Cisco Secure FTD Software and have syslog logging enabled for message 419002. Logging message 419002 is enabled by default when logging is enabled globally.

For information about which Cisco software releases are vulnerable, see the Fixed Software section of this advisory.

Determine the Device Configuration

To determine whether a device is affected by this vulnerability, use the following steps.

1. Use the show logging | include syslog logging command on the device CLI to verify if syslog logging is enabled globally. If the output of this command includes enabled, as shown in the following example, syslog logging is enabled globally. Proceed to Step 2.

ASAv1# show logging | include syslog
Syslog logging: enabled

If the output indicates that logging is disabled, the device is not affected.

2. Use the show logging message 419002 command to determine if logging is specifically enabled for syslog message 419002. If the output of this command shows that logging is enabled for syslog message 419002, note the default level that the device uses when logging this message. The following example output shows that syslog message 419002 is enabled at default level warnings. Proceed to Step 3.

ASA# show logging message 419002
syslog 419002: default-level warnings (enabled),standby 
logging (disabled)

If logging for this message is disabled, the device is not affected.

3. Use the show logging | include logging: level command to determine if logging to any log destination is enabled and confirm the corresponding logging level.

The following example output shows that logging is enabled for destination Console at level errors and for destination Buffer at level warnings:

ASA# show logging | include logging: level
    Console logging: level errors, 301 messages logged
    Buffer logging: level warnings, 265964 messages logged

If logging to any destination is enabled at the logging level that was confirmed for syslog message 419002 in Step 2 or higher, the device is affected.

In the example in Step 3, logging to destination Buffer is configured to level warnings, which corresponds to the logging level for syslog message 419002 in the example in Step 2. The device in this example would be considered vulnerable.

In the example in Step 3, logging to destination Console is configured at level errors, which is below the logging level for syslog message 419002 in the example in Step 2. If this were the only enabled logging destination on the device, syslog message 419002 would never be logged, and the device would not be considered vulnerable.

Empty output of the show logging | include logging: level command indicates that the device is not affected.

For more information on logging configuration, see the Logging chapter in CLI Book 1: Cisco Secure Firewall ASA Series General Operations CLI Configuration Guide, 9.24, the Syslog section in the Cisco Secure Firewall Management Center Device Configuration Guide, or the Configuring System Logging Settings section in the Cisco Secure Firewall Device Manager Configuration Guide.

Workarounds and temporary mitigations

There is a workaround that addresses this vulnerability. Rate limit in Cisco Secure Firewall ASA Software or Cisco Secure FTD Software using the methods described in the following sections.

Cisco Secure Firewall ASA Software

For devices that are running Cisco Secure Firewall ASA Software, append in global configuration mode and manually rate limit using the logging rate-limit 100 1 message 419002 command.

In the following example, message 419002 is limited to a rate of 100 messages per second, which will prevent successful exploitation of this vulnerability:

ASA(config)# logging rate-limit 100 1 message 419002

Cisco Secure FTD Software

For devices that are running Cisco Secure FTD Software, use one of the following options:

  • Choose Secure Firewall Management Center (FMC) > Devices > Platform Settings > Rate Limit > Syslog Level and deploy the appropriate policies. For more information, see Configure Logging on FTD via FMC.

  • Choose Firewall Device Manager (FTD) > Device > System Settings > Logging and rate limit message 419002 to 100 messages per second. For more information, see Configure and Verify Syslog in Firepower Device Manager.

While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations.

Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

Fixed software

Cisco considers any workarounds and mitigations (if applicable) to be temporary solutions until an upgrade to a fixed software release is available. To remediate this vulnerability and avoid future exposure as described in this advisory, Cisco strongly recommends that customers upgrade to the fixed software indicated in this advisory.

Fixed Releases

In the following table, the left column lists Cisco software releases. The center column lists hot fixes that are affected by the vulnerabilities that are described in this advisory, and the right column indicates the first software release that includes the fix for these vulnerabilities. Customers who installed one of the listed hot fix releases must install the listed first fixed release.

Cisco Secure Firewall ASA Software Release

Affected Hot Fix Release

First Fixed Release

9.16 and earlier

N/A

9.16.4.103

9.18

9.18.4.135

9.18.4.94

9.20

9.20.4.235

9.20.4.49

9.22

9.22.3.191

9.22.3.26

9.23

9.23.1.195

9.23.1.211

9.23.1.47

9.24

9.24.1.155

9.24.1.221

9.24.1.26

In the following table, the left column lists Cisco software releases. The right column indicates whether a release is affected by the vulnerabilities that are described in this advisory and the first release that includes the fix for these vulnerabilities.

Cisco Secure FTD Software Release and Secure FMC Software Release

First Fixed Release

7.0 and earlier

7.0.10

7.2

7.2.12

7.4

7.4.8

7.6

7.6.6

7.7

7.7.13

10.0

10.0.2

10.1

10.1.0

Cisco strongly recommends that customers upgrade to the first fixed releases in the preceding tables because they include fixes for multiple vulnerabilities. For more information, see Cisco Secure Firewall Adaptive Security Appliance, Secure Firewall Threat Defense, and Secure Firewall Management Center Software Hardening Release: September 2026.

Cisco Secure Firewall ASA, Secure FMC, and Secure FTD Software

To help customers determine their exposure to vulnerabilities in Cisco Secure Firewall ASA, Secure FMC, and Secure FTD Software, Cisco provides the Cisco Software Checker. This tool identifies any Cisco security advisories that impact a specific software release and the earliest release that fixes the vulnerabilities that are described in each advisory (“First Fixed”).

If applicable, the tool also returns the earliest release that fixes all the vulnerabilities that are described in all the advisories that the Software Checker identifies (“Combined First Fixed”).

To use the tool, go to the Cisco Software Checker page and follow the instructions. Alternatively, use the following form to search for vulnerabilities that affect a specific software release. To use the form, follow these steps:

  1. Choose which advisories the tool will search-all advisories, only advisories with a Critical or High Security Impact Rating (SIR), or only this advisory.

  2. Choose the appropriate software.

  3. Choose the appropriate platform.

  4. Enter a release number-for example, 9.20.3.4 for Cisco Secure Firewall ASA Software or 7.4.2 for Cisco Secure FTD Software.

  5. Click Check.

For instructions on upgrading a Cisco Secure FTD device, see the appropriate Cisco Secure FMC upgrade guide.

Exploitation status

The Cisco Product Security Incident Response Team (PSIRT) is not aware of any public announcements or malicious use of the vulnerability that is described in this advisory.

Read the collected advisory