Unbiased headlines. Facts, not spin.
Unbiased Headlines is an independently owned news organization. We bring you the facts, not opinions, written fresh from 110+ named sources. Sources linked so you can verify it yourself.
Attackers Used Public Exploit on Cisco Expressway Flaw to Breach Russian Organization, F6 Says

A critical flaw in Cisco Expressway has gone from advisory to attack. F6, a Russian cybersecurity company, published a report Thursday, Nov. 19, saying attackers exploited CVE-2026-76466 to take root control of Expressway devices at a Russian organization and then spread into its internal network.
F6 describes it as what appears to be the first known exploitation of the bug in the wild. It was not a zero-day. Cisco released patches on October 21, 2026.
What the flaw does
The bug carries a CVSS score of 9.8. Cisco's advisory says an unauthenticated, remote attacker with network access to an Expressway device could run arbitrary operating system commands as root.
Cisco attributes the problem to persistent cookies, plus insufficient validation of client certificates when TLS Verify Mode is set to Enabled for clustering. In Cisco's words, an attacker holding the cookies "could exploit this vulnerability by connecting to the database service and invoking specific remote procedure call (RPC) commands."
The public proof-of-concept, as analyzed by security firm Ostorlab, is more blunt. It says a maintenance node identity and its cookie are compiled into the software and are identical on every installation of the affected release. The CVE carries the weakness classification CWE-798, use of hard-coded credentials.
The vulnerable component is the cluster database service, which runs on Erlang and listens on TCP ports 4371 and 4372. A standalone Expressway falls outside the advisory's vulnerable set, according to Ostorlab. Expressway-C and Expressway-E nodes in a cluster are the exposed configuration.
How the intrusion played out
Exploit code appeared on GitHub on November 5, according to the security firm Secure.com. F6 says the attack it observed came after that release.
The attackers first compromised two internet-facing Expressway X15.5.3 devices, F6 said. Through one of them they reached two more cluster nodes on the organization's internal network. That is four devices total.
The cluster design is what made the jump possible. Nodes trust each other so they can replicate registrations and call state, so a rooted edge machine can talk to the core machines behind it.
Once inside, the attackers ran custom Python scripts. F6 says the scripts scanned the network, hunted for accessible SMB shares, interacted with SQL Server and WinRM, and searched GitLab repositories for credentials and other sensitive data.
F6 also says the scripts were changed during the intrusion, and that comments and descriptions of fixes inside the code suggest AI tools helped write them. That is F6's assessment of the code, not a confirmed finding about how it was made.
No known threat actor or group has been tied to the attack. Neither F6 nor Cisco has named one.
What F6 published for defenders
F6 released indicators of compromise: two IP addresses, Python scripts staged under a specific disk path, and a "nodeup" entry in the Erlang system log (erlang.log) on affected devices. F6 says that entry shows a connection from an Erlang node whose identifier matches the known exploitation method.
A hit is a lead and a clean log is not proof of safety. A failed attempt may leave no trace.
"This incident demonstrates that compromise of a perimeter device can open a path for an attacker to an organization's critical systems," F6 said. The firm argues protection needs properly configured segmentation and infrastructure monitoring on top of timely patching.
What admins are being told to do
The fix is X15.5.20 or later on every node in a cluster. Ostorlab says the X14 branch and earlier have no fixed release and must be migrated.
Secure.com, which sells managed security services, says Cisco lists no workaround. It recommends restricting TCP ports 4371 and 4372 to cluster peers only. Ostorlab suggests testing whether a workstation or user network can reach those ports. A successful connection is the exposure to close first.
F6 advises isolating affected systems, scoping the intrusion and blocking lateral movement paths. Secure.com adds that anyone who finds a match should assume the attacker went beyond the gateway.
The timeline problem
About four weeks passed between Cisco's patch and the first reported breach. Roughly two weeks of that came after exploit code went public. The victim organization had both windows to patch and, per F6, did not.
Secure.com says the flaw was not listed in CISA's Known Exploited Vulnerabilities catalog as of Nov. 20. The open questions are whether CISA adds it, who the attackers are, and whether other organizations running clustered Expressway systems on X15.5.3 or earlier have already been hit. F6 has so far reported one victim.
Sources used for this briefing
7 links from 6 independent newsrooms (syndicated copies of the same report count once)
These are the sources it draws on, linked so you can verify.