Skip to content

A month-old Cisco Expressway RCE is now being exploited

Security researchers at F6 say attackers breached clustered Expressway devices within days of a public proof-of-concept, even though Cisco's own advisory still says it has no evidence of exploitation.

Source: Cisco

Cisco disclosed CVE-2026-76466 on 21 October: an unauthenticated, critical (CVSS 9.8) flaw in clustered Cisco Expressway-C and Expressway-E devices. The database service relies on persistent cookies for authentication and does not properly validate client certificates when TLS Verify Mode is on for clustering, so an attacker with one of those cookies can send RPC commands to the database service and run arbitrary OS commands as root. There’s no workaround, only a fix: Expressway X15.5.20. Devices on X14 and earlier need to migrate entirely.

Russian security firm F6 now reports that attackers breached two internet-facing Expressway X15.5.3 devices at a Russian organisation shortly after a proof-of-concept exploit went public, then pivoted to two other nodes on the same cluster and staged custom scripts for further lateral movement, editing them on the fly during the attack. Cisco’s advisory, still at version 1.0, says it is “not aware of any public announcements or malicious use” of the bug.

Why it matters: if you run Expressway in a cluster, check your version now rather than trusting Cisco’s advisory text, which hasn’t caught up with F6’s findings. F6 suggests blocking TCP 4371 to 4372 at the firewall if you can’t patch immediately, and checking the Erlang system log for signs of compromise.

The caveat: this isn’t on CISA’s Known Exploited Vulnerabilities list yet, and F6 has only confirmed one victim publicly. Treat it as an early warning, not evidence of mass exploitation.

Share

Related reading

More from The Wire

All briefs

A Linux KVM bug let one VM read 127GB of host memory

A bug bounty researcher used a four-year-old stale pointer in nested virtualization to read host kernel memory from inside an ordinary cloud VM. DigitalOcean disclosed and patched it as CVE-2026-99312.

via DigitalOcean