⚠ Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● Critical · CVSS 9.8

How to Fix CVE-2026-20184: Certificate validation in Cisco Webex Meetings

By Sai Kiran Pandrala. Last verified: 2026-05-25.

⚡ At a glance
Severity9.8 (Critical)
Actively exploited?No public listing in CISA KEV
AffectedCisco 39.7.7, 39.9, 40.4.10, 39.6, 40.6.2, 39.8.2, 39.8.4, 40.1, 39.11, 39.7.4, 39.9.1, 40.4, 40.6, 39.7, 39.8, 39.8.3, 40.2, 39.10, 42.6, 42.7, 42.8, 42.9, 42.10, 42.11, 42.12, 43.1, 43.2, 43.3, 43.4, 43.4.1, 43.4.2, 43.5.0, 43.6.0, 43.6.1, 43.7, 43.8, 43.9, 43.10, 43.11, 43.12, 44.1, 44.2, 44.3, 44.4, 44.5, 44.6, 44.7, 44.8, 44.9, 44.10, 44.11, 44.12, 45.1, 45.2, 45.3, 45.4
Fixed inSee vendor advisory
Type (CWE)CWE-295: Improper Certificate Validation

What is CVE-2026-20184?

A vulnerability in the integration of single sign-on (SSO) with Control Hub in Cisco Webex Services could have allowed an unauthenticated, remote attacker to impersonate any user within the service. This vulnerability existed because of improper certificate validation. Prior to this vulnerability being addressed, an attacker could have exploited this vulnerability by connecting to a service endpoint and supplying a crafted token. A successful exploit could have allowed the attacker to gain unauthorized access to legitimate Cisco Webex services.

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 39.7.7, 39.9, 40.4.10, 39.6, 40.6.2, 39.8.2, 39.8.4, 40.1, 39.11, 39.7.4, 39.9.1, 40.4, 40.6, 39.7, 39.8, 39.8.3, 40.2, 39.10, 42.6, 42.7, 42.8, 42.9, 42.10, 42.11, 42.12, 43.1, 43.2, 43.3, 43.4, 43.4.1, 43.4.2, 43.5.0, 43.6.0, 43.6.1, 43.7, 43.8, 43.9, 43.10, 43.11, 43.12, 44.1, 44.2, 44.3, 44.4, 44.5, 44.6, 44.7, 44.8, 44.9, 44.10, 44.11, 44.12, 45.1, 45.2, 45.3, 45.4). If your build sits inside that range, the device is exposed and should be upgraded.

How to fix CVE-2026-20184

The primary fix is to upgrade Cisco Webex Meetings 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-webex-cui-cert-8jSZYhWL
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-webex-cui-cert-8jSZYhWL
#!/usr/bin/env bash
# CVE-2026-20184 fix runbook for Cisco Cisco Webex Meetings
# 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-20184-$(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-20184-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

Other vulnerabilities in the same area that are worth patching alongside this one:

Is CVE-2026-20184 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?

9.8 (critical). 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

*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.*