CVE-2026-20080: Cisco Ultra-Reliable Wireless Backhaul · Uncontrolled Resource Consumption
Affects Cisco Ultra-Reliable Wireless BackhaulSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 31% 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:N/I:N/A:LExploitation evidence
Disclosed: evidence found.
CVE published 21 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| CiscoCisco Ultra-Reliable Wireless Backhaul | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2026-20080, organizations should implement several specific measures beyond generic advice: 1) Deploy network-level rate limiting and connection throttling on SSH ports to prevent flood attacks, using firewalls or intrusion prevention systems capable of detecting and blocking excessive SSH connection attempts. 2) Restrict SSH access to trusted management networks or specific IP addresses using access control lists (ACLs) to reduce exposure to unauthenticated attackers. 3) Monitor SSH traffic patterns for anomalies indicative of flooding or DoS attempts, enabling rapid detection and response. 4) Where possible, implement out-of-band management channels or redundant access paths to ensure continued device management if SSH becomes unavailable. 5) Apply Cisco-provided patches or firmware updates promptly once released to address the underlying vulnerability. 6) Consider deploying SSH service hardening configurations if supported, such as connection rate limits or fail2ban-like protections. 7) Conduct regular security assessments and penetration testing focused on management interfaces to validate the effectiveness of controls. These targeted mitigations will reduce the risk of SSH service disruption and maintain operational continuity.
Description
A vulnerability in the SSH service of Cisco IEC6400 Wireless Backhaul Edge Compute Software could allow an unauthenticated, remote attacker to cause the SSH service to stop responding. This vulnerability exists because the SSH service lacks effective flood protection. An attacker could exploit this vulnerability by initiating a denial of service (DoS) attack against the SSH port. A successful exploit could allow the attacker to cause the SSH service to be unresponsive during the period of the DoS attack. All other operations remain stable during the attack.