Cisco Expressway Flaw CVE-2026-76466 Is Now Exploited, F6 Says, a Month After Cisco’s Fix
F6 says attackers used a 9.8-rated flaw in clustered Cisco Expressway servers to break into a company in Russia and reach other cluster nodes. Cisco's advisory still says it knows of no attacks. Fixed release, who is exposed, and what to check.

A critical flaw in Cisco Expressway, patched a month ago, is now being used in real attacks, according to the Russian security firm F6. The flaw, CVE-2026-76466, scores 9.8 out of 10 and lets someone with network access run commands as root on Expressway servers that are set up in a cluster. F6 says attackers broke into a company in Russia through two internet-facing Expressway servers soon after a public exploit appeared, then used them to reach other servers inside the network. Cisco has not yet changed its advisory, which still says it knows of no malicious use. The fix is Expressway X15.5.20, and customers on X14 or earlier have no in-place fix and must move to a newer release.
#Where each side stands
Cisco published its advisory, titled “Cisco Expressway Series Remote Code Execution Vulnerability”, on 21 October 2026. It covers Expressway-C and Expressway-E, in both virtual and appliance form, but only “if they are running a vulnerable release and have the devices configured in a cluster”, in Cisco’s words. The advisory has had no revision since that first version. It says there are no workarounds, and as of that version Cisco’s product security team “is not aware of any public announcements or malicious use”.
On 18 November F6 said it had recorded the first exploitation of the flaw, in an attack on a company in Russia, and SecurityWeek reported the story on 19 November. According to F6, the attackers hit Expressway devices running X15.5.3 shortly after a public exploit appeared. SecurityWeek says that exploit is posted on GitHub. Neither report gives the date it was published, and we have not tested it or reproduced any of it. F6 did not attribute the attack to a known group, and nothing we have read names who the victim is.
The two accounts do not contradict each other so much as sit a month apart. Cisco’s statement dates from the day it published the fix; F6’s report is from a month later, after the exploit became public. We would expect Cisco to update its advisory, but it had not when we checked on the morning of 20 November, and Cisco had not replied to SecurityWeek’s request for comment when that story went out.
#What F6 says the attackers did
F6’s account of the intrusion is the useful part for defenders, because it shows what happens after the first server falls. The attackers first compromised two Expressway devices that faced the internet. Through one of them, F6 says, they reached two other nodes of the same cluster inside the internal network. With root access on those machines they ran custom Python scripts to scan the network and to look for Windows file shares, and to interact with SQL Server and Windows Remote Management. They also searched GitLab repositories for credentials and other confidential data.
F6 adds that the attackers edited their scripts during the attack, and that the code contained comments and fix notes suggesting an AI assistant was used to write it. That is F6’s observation about one set of scripts, and we have no way to check it. It does not change what you should do.
It does change one assumption. Many organisations treat a collaboration gateway as a plumbing box that carries video calls and little else. An Expressway cluster that straddles the internet edge and the internal network is a bridge between the two, and an attacker who owns it starts with a foothold already inside.
#What the flaw is, as far as Cisco says
Cisco describes the problem as being in the database service feature. It names two causes: “the use of persistent cookies”, and “insufficient validation of client certificates when the TLS Verify Mode is set to Enabled for clustering”. An attacker holding the cookies could connect to the database service and invoke certain remote procedure calls, and from there execute operating system commands as root. Cisco credits Stefan Aleksic of Jane Street with reporting it.
Our reading, which is a reading and not something Cisco states: the identifier in the advisory’s own address contains the words “static-cred”, which points to a fixed credential that every affected device shares. If so, that would explain why the flaw needs no password from the attacker and why it only bites on clusters, where nodes must be able to talk to each other’s database service. The fix presumably changes how that trust is established. Cisco has not said so, and we would not rely on this beyond using it to judge where the exposure lies: the cluster ports, not the web page.
F6 identifies those ports. Its advice, which is not a Cisco workaround, is that if you cannot update now, you should block TCP ports 4371 to 4372 at the firewall for everything except the addresses of your own cluster nodes.
#Is yours exposed?
Three conditions have to hold: it is an Expressway-C or Expressway-E, it runs X15.5.3 or earlier, and it is configured in a cluster. Cisco’s advisory does not say how to check the last of these, so ask whoever built your Expressway deployment, or look at its clustering configuration in the administration interface. If you run a single, unclustered node, Cisco’s wording means you are outside the vulnerable condition. We would still update it, because the same fixed release also carries Cisco’s October hardening changes for eight other issues. Cisco says those were found in internal testing and are not known to be exploited, and that the fixed version for them is also X15.5.20.
There is a trap in the version table. Cisco lists a first fixed release only for X15.5.3 and earlier, which is X15.5.20. For X14 and earlier it says only “Migrate to a fixed release”. That is a migration project, not a patch, so budget for it rather than waiting for a fix to appear.
#What to do today
- List every Expressway you run, including the one a previous supplier installed and nobody has opened since. Record the release and whether it forms part of a cluster.
- Update clustered nodes to X15.5.20, or schedule the migration for X14 and earlier. Update all the nodes of a cluster, not only the one that faces the internet. Take a copy of the system logs off the device before you upgrade, in case you need them.
- Close the cluster ports in the meantime. F6’s interim measure is to restrict TCP 4371 to 4372 so only your own cluster nodes can reach them. Treat this as a stopgap that we have not tested, and remember Cisco lists no workaround.
- Look for signs of a break-in. F6 gives one indicator: an entry reading
nodeup,'wombat@127.0.0.1'in the Erlang system log on the device, which it says matches a known way of exploiting this flaw. It also names Python script files under/mnt/harddisk/and two network addresses, 66.179.31[.]32 and 18.130.47[.]116, which F6 lists in its release. F6 itself says other logs should be checked to confirm a compromise, and the absence of these entries is not proof you are clean. - If you find anything, assume wider damage. By F6’s account the attackers moved to Windows shares, SQL Server and GitLab. In our view, anything reachable from the Expressway nodes, and every credential stored on or visible to them, should be treated as exposed until an incident responder says otherwise.
#Our view: patch first, then check, and do not wait for Cisco
We think this is a patch-today problem for anyone with a clustered Expressway, even though the evidence of attacks is one firm’s report of one victim. The reasons are simple. A public exploit exists. The fix has been out for a month, so the window for patching calmly has closed. And do not read Cisco’s advisory as an all-clear: it says Cisco knew of no malicious use on the day it published, which is not the same as saying none has happened since.
The week shows a pattern worth noting. Google reported on 19 November that a suspected Chinese group had been exploiting the VMware vCenter bypass for months before it was patched, which we cover in our vCenter story. The Expressway case is the reverse order: patch first, public exploit second, attack third. Both ended in the same place, with an attacker inside a system that connects the outside to the inside. We expect to see more of the second pattern, with exploit code appearing within weeks of an advisory. What would prove us wrong is a run of critical patches that go a quarter without a public exploit.
For UK organisations, the question of how quickly a critical fix has to be applied is usually settled by a certification or a contract, so it is worth reading our plain-English guide to Cyber Essentials if you are not sure how your own timeline is judged.
#A question for your provider
If a managed service provider or your telephony supplier runs your Cisco collaboration setup, send them this, word for word: “Do we run Cisco Expressway in a cluster, which release is it on, and has anyone checked its logs for the CVE-2026-76466 indicators that F6 published?” If the answer is “we do not know”, that is also an answer.
#What we do not know yet
- How many organisations have been attacked. F6 reports one, in Russia, and no other victim has been named.
- When the public exploit appeared, and who wrote it. Neither report says.
- Whether Cisco will revise its advisory to say the flaw is exploited. It had not by 20 November.
- Whether the flaw will be added to the US cyber agency CISA’s Known Exploited Vulnerabilities list. It was not in the catalogue release we read, dated 18 November.
- Exactly how the attack works. Cisco has not published a technical description beyond the summary above.
We will update this story if Cisco confirms exploitation or if more victims come forward.
Evidence trail
Sources and verification
Primary documentation and external technical references used in this article.
- 01Cisco, Cisco Expressway Series Remote Code Execution Vulnerability (cisco-sa-vcs-static-cred-hr7EWZ8t), 21 October 2026sec.cloudapps.cisco.com
- 02Cisco, Cisco Expressway Series Security Hardening Release: October 2026sec.cloudapps.cisco.com
- 03F6, press release on the first exploitation of CVE-2026-76466 (in Russian), 18 November 2026f6.ru
- 04SecurityWeek, Hackers Exploit Cisco Expressway Vulnerability Soon After PoC Release, 19 November 2026securityweek.com
- 05CISA Known Exploited Vulnerabilities cataloguecisa.gov
About this page
Credited to
Dates
Published
Corrections
No corrections are listed for this page. Some review sweeps corrected pages without naming each one; those are in the corrections log.
More news
All news
Artificial IntelligenceGoogle Now Keeps Gemini Chats for About Two Months Even With History Off, Up From 72 Hours



Was this useful?
Reports go to the site owner and are used to correct pages. Corrections are listed at /corrections.
Get new fixes by email.
New runbooks, configuration traps and fixes from KBY Technologies, about twice a week.
Comments
Add a thoughtful note on Cisco Expressway Flaw CVE-2026-76466 Is Now Exploited, F6 Says, a Month After Cisco’s Fix. Comments are checked for spam and held for moderation before appearing.