Skip to main content
VulnerabilityPublished

CVE-2026-20009: Cisco Secure Firewall Adaptive Security Appliance (ASA) Software · Improper Neutralization of Special Elements

Affects Cisco Secure Firewall Adaptive Security Appliance (ASA) SoftwareSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.3 Medium.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
CiscoCisco Secure Firewall Adaptive Security Appliance (ASA) SoftwareAffected
  • 9.17.1 – 9.23.1.13
82 affected builds
Fixed in–

AI-suggested

  1. Apply Cisco's security updates and patches for ASA software versions affected by CVE-2026-20009 as soon as they become available. Regularly check Cisco advisories for updates.
  2. Restrict SSH access to Cisco ASA devices by implementing network segmentation and firewall rules that limit SSH connections to trusted management networks or IP addresses.
  3. Enforce strong username management practices, including avoiding predictable usernames and regularly auditing authorized public keys associated with user accounts.
  4. Enable multi-factor authentication (MFA) for device management access where supported to add an additional layer of security beyond SSH keys.
  5. Monitor SSH login attempts and device logs for unusual authentication activity or repeated failed attempts that could indicate exploitation attempts.
  6. Consider disabling SSH key-based authentication temporarily if feasible and switching to alternative secure management methods until patches are applied.
  7. Conduct regular security assessments and penetration testing focused on network perimeter devices to detect potential exploitation or misconfigurations.
  8. Educate network administrators on this vulnerability and the importance of safeguarding SSH credentials and keys.

Description

A vulnerability in the implementation of the proprietary SSH stack with SSH key-based authentication in Cisco Secure Firewall Adaptive Security Appliance (ASA) Software could allow an unauthenticated, remote attacker to log in to a Cisco Secure Firewall ASA device and execute commands as a specific user. This vulnerability is due to insufficient validation of user input during the SSH authentication phase. An attacker could exploit this vulnerability by submitting crafted input during SSH authentication to an affected device. A successful exploit could allow the attacker to log in to the device as a specific user without the private SSH key of that user. To exploit this vulnerability, the attacker must possess a valid username and the associated public key. The private key is not required. Notes: Exploitation of this vulnerability does not provide the attacker with root access. The authentication, authorization, and accounting (AAA) configuration command auto-enable is not affected by this vulnerability.  

References

Community reviews

Loading reviews…