How to Fix CVE-2026-20152: Authentication bypass by primary weakness flaw in Cisco Secure Web Appliance
By Sai Kiran Pandrala. Last verified: 2026-05-25.
| Severity | 5.3 (Medium) |
|---|---|
| Actively exploited? | No public listing in CISA KEV |
| Affected | Cisco 11.8.0-453, 12.5.3-002, 12.0.3-007, 12.0.3-005, 14.1.0-032, 14.1.0-047, 14.1.0-041, 12.0.4-002, 14.0.2-012, 11.8.0-414, 12.0.1-268, 11.8.1-023, 11.8.3-021, 11.8.3-018, 12.5.1-011, 11.8.4-004, 12.5.2-007, 12.5.2-011, 14.5.0-498, 12.5.4-005, 12.5.4-011, 12.0.5-011, 14.0.3-014, 12.5.5-004, 12.5.5-005, 12.5.5-008, 14.0.4-005, 14.5.1-008, 14.5.1-016, 15.0.0-355, 15.0.0-322,... |
| Fixed in | See vendor advisory |
| Type (CWE) | CWE-305: Authentication Bypass by Primary Weakness |
What is CVE-2026-20152?
A vulnerability in the authentication service feature of Cisco AsyncOS Software for Cisco Secure Web Appliance could allow an unauthenticated, remote attacker to bypass authentication policy requirements. This vulnerability is due to improper validation of user-supplied authentication input in HTTP requests. An attacker could exploit this vulnerability by sending HTTP requests that contain specific authentication requests to an affected device. A successful exploit could allow the attacker to bypass policy enforcement on the device.
Am I affected?
From the device CLI, run the version check:
# Cisco IOS/IOS XE
show version | include Version
# FortiGate (FortiOS)
get system status
# Palo Alto (PAN-OS)
show system info | match sw-version
# Juniper (Junos)
show version
Compare what you see against the Affected row above (Cisco 11.8.0-453, 12.5.3-002, 12.0.3-007, 12.0.3-005, 14.1.0-032, 14.1.0-047, 14.1.0-041, 12.0.4-002, 14.0.2-012, 11.8.0-414, 12.0.1-268, 11.8.1-023, 11.8.3-021, 11.8.3-018, 12.5.1-011, 11.8.4-004, 12.5.2-007, 12.5.2-011, 14.5.0-498, 12.5.4-005, 12.5.4-011, 12.0.5-011, 14.0.3-014, 12.5.5-004, 12.5.5-005, 12.5.5-008, 14.0.4-005, 14.5.1-008, 14.5.1-016, 15.0.0-355, 15.0.0-322,...). If your build sits inside that range, the device is exposed and should be upgraded.
How to fix CVE-2026-20152
The primary fix is to upgrade Cisco Secure Web Appliance to the patched build. Use the commands for your platform below; the patched version listed in the vendor advisory is: See vendor advisory.
Cisco IOS / IOS XE
# Vendor advisory: https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-wsa-auth-bypass-6YZkTQhd
enable
show version | include Version
copy running-config startup-config
copy tftp: flash:
! upload the patched image, then:
boot system flash:<patched-image>.bin
reload
Complete operator runbook (network appliance)
Run this from your management workstation (Linux/macOS or Windows with a TFTP server reachable). It shells into the device, backs up the running config, transfers the patched image, and reloads.
# Vendor advisory: https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-wsa-auth-bypass-6YZkTQhd
#!/usr/bin/env bash
# CVE-2026-20152 fix runbook for Cisco Cisco Secure Web Appliance
# Target build: the patched build
set -euo pipefail
DEVICE="${1:?usage: $0 <device-ip> <patched-image-file> <tftp-server-ip>}"
IMAGE="${2:?patched image filename required}"
TFTP="${3:?tftp server ip required}"
LOG="/var/log/cve-2026-20152-$(date +%Y%m%d-%H%M%S).log"
echo "[1/4] Pulling current config from $DEVICE"
ssh admin@"$DEVICE" "show version" | tee -a "$LOG"
ssh admin@"$DEVICE" "copy running-config tftp://$TFTP/cve-2026-20152-pre.cfg"
echo "[2/4] Uploading patched image $IMAGE via TFTP"
ssh admin@"$DEVICE" "copy tftp://$TFTP/$IMAGE flash:$IMAGE" | tee -a "$LOG"
echo "[3/4] Setting boot image and reloading"
ssh admin@"$DEVICE" "configure terminal
boot system flash:$IMAGE
end
write memory
reload" | tee -a "$LOG"
echo "[4/4] Wait ~5 minutes, then verify"
sleep 300
ssh admin@"$DEVICE" "show version | include Version" | tee -a "$LOG"
echo "Compare reported version against the patched build"
If you can't patch immediately
If you cannot apply the patched version today, restrict exposure with one of the following runnable controls. None replace the patch.
Network appliance ACL
# Cisco IOS example: restrict management plane to a trusted subnet
configure terminal
access-list 99 permit 10.0.0.0 0.255.255.255
line vty 0 15
access-class 99 in
end
write memory
Service-level fallback
# If the affected feature is optional, stop the service until the patch is applied
sudo systemctl stop cisco
sudo systemctl disable cisco
How to verify the fix worked
# Linux
cisco --version 2>/dev/null || dpkg -s cisco | grep -i version
rpm -q cisco 2>/dev/null || true
# Windows
winget list | findstr /I "cisco"
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5
Expected: the reported version is at or above the patched build documented in the advisory. Restart any services that loaded the old library (systemctl restart <service> on Linux, restart the Windows service or reboot when prompted). For network appliances, run show version on the device and confirm the build matches the patched release.
Frequently asked questions
Related fixes
Other vulnerabilities in the same area that are worth patching alongside this one:
- How to Fix CVE-2026-20005: Missing report of error condition in Cisco Secure Firewall Threat Defense (FTD). — Missing report of error condition in Cisco Secure Firewall Threat Defense (FTD).
- How to Fix CVE-2026-20199: Critical Vulnerability in Cisco ThousandEyes Enterprise Agent — Critical Vulnerability in Cisco ThousandEyes Enterprise Agent
- How to Fix CVE-2026-20054: Loop with unreachable exit condition ('infinite loop') in Cisco Cyber Vision , Loop with unreachable exit condition ('infinite loop') in Cisco Cyber Vision
- How to Fix CVE-2026-20073: Improper access control in Cisco Secure Firewall Adaptive Security Appliance (ASA). , Improper access control in Cisco Secure Firewall Adaptive Security Appliance (ASA).
- How to Fix CVE-2026-20082: Missing release of resource after effective lifetime in Cisco Secure Firewall. , Missing release of resource after effective lifetime in Cisco Secure Firewall.
Is CVE-2026-20152 actually being exploited?
According to the data sources above, no public confirmation of in-the-wild exploitation at this time. Either way, the fix is the same: apply the vendor patch.
Do I need to reboot after patching?
For OS or kernel updates, yes. For most userland packages a systemctl restart <service> is enough. Any process that loaded the old shared library keeps using it until restarted, so when in doubt, reboot.
What is the CVSS score?
5.3 (medium). Refer to the vendor advisory for the exact vector string.
Where is the official advisory?
See the References section at the bottom of this page; the vendor's URL is the authoritative source for affected builds and patched versions.
References
- Official vendor advisory: https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-wsa-auth-bypass-6YZkTQhd
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-20152
*Written by Sai Kiran Pandrala. Assembled from the official vendor advisory, NVD record, and CISA KEV listing on 2026-05-25. Always confirm against the vendor's advisory before applying changes in production.*