{"id":4455,"date":"2026-11-20T06:33:16","date_gmt":"2026-11-20T14:33:16","guid":{"rendered":"https:\/\/cyber.mag212.com\/cisco-expressway-cve-2026-76466-exploited-hard-coded-credential\/"},"modified":"2026-11-20T06:33:16","modified_gmt":"2026-11-20T14:33:16","slug":"cisco-expressway-cve-2026-76466-exploited-hard-coded-credential","status":"publish","type":"post","link":"https:\/\/cyber.mag212.com\/fr\/cisco-expressway-cve-2026-76466-exploited-hard-coded-credential\/","title":{"rendered":"Exploitation de la vuln\u00e9rabilit\u00e9 Cisco Expressway CVE-2026-76466\u00a0: identifiants de cluster cod\u00e9s en dur, quatre appareils compromis et solution de d\u00e9pannage."},"content":{"rendered":"\n<p class=\"wp-block-paragraph\"><em>From the <a href=\"https:\/\/cyber.mag212.com\/the-keys-to-vsphere-mag212-cyber-daily-november-20-2026\/\">MAG212 CYBER Daily, 20 November 2026<\/a>. Every command is copied from official documentation or the cited analysis and was <strong>not tested by MAG212<\/strong>; run it only on systems you are authorised to administer.<\/em><\/p>\n\n\n\n<p class=\"m2-status wp-block-paragraph\"><strong>Status:<\/strong> <strong>Fixed on 21 October 2026<\/strong> in Expressway X15.5.20; X14 and earlier must migrate. <strong>Exploitation reported on 19 November<\/strong> by Russian security firm F6: one organisation, four devices. We could not load F6&#8217;s own report; details come from The Hacker News and Ostorlab. Cisco&#8217;s advisory still says it is &#8220;not aware of malicious use&#8221;. A public proof of concept has existed since 5 November. CVSS 9.8. <sup><a href=\"#src-1\">[1]<\/a><\/sup><sup><a href=\"#src-2\">[2]<\/a><\/sup><sup><a href=\"#src-3\">[3]<\/a><\/sup><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What happened<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Cisco&#8217;s advisory cisco-sa-vcs-static-cred-hr7EWZ8t, published 21 October, describes CVE-2026-76466: a hard-coded credential (CWE-798) in clustered Expressway that lets an unauthenticated remote attacker run commands as root. Cisco blames &#8220;the use of persistent cookies&#8221; and insufficient client-certificate checking &#8220;when TLS Verify Mode is set to Enabled for clustering&#8221;. <sup><a href=\"#src-1\">[1]<\/a><\/sup><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">On 19 November The Hacker News, citing F6, reported the first known attacks. <sup><a href=\"#src-2\">[2]<\/a><\/sup><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Why this matters<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Expressway sits at the network edge so that video and voice calls can cross the firewall. Root on that box is a foothold with a view of both sides. The fix has existed for a month and a public proof of concept for two weeks, so any unpatched cluster is now an easy target. Cisco&#x27;s advisory still says it knows of no malicious use, so teams that only watch vendor advisories may not see the urgency. <em>(MAG212 analysis)<\/em><\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><a href=\"https:\/\/cyber.mag212.com\/wp-content\/uploads\/2026\/11\/cisco-20nov-diagram.png\"><img decoding=\"async\" src=\"https:\/\/cyber.mag212.com\/wp-content\/uploads\/2026\/11\/cisco-20nov-diagram.png\" alt=\"A static password, four breached devices. Diagram by MAG212 CYBER.\"\/><\/a><figcaption class=\"wp-element-caption\">Diagram: MAG212 CYBER. Solid red = observed or confirmed; dashed amber = reported or unverified; green = recommended control.<\/figcaption><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">How the attack works<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Expressway cluster members share a database service that listens on TCP 4372 and uses Erlang\/OTP distribution. According to Ostorlab&#8217;s analysis, the public proof of concept connects as an Erlang node using a node name and cookie, both &#8220;wombat&#8221;, that are identical on every affected installation. Erlang distribution lets a trusted node run code on its peers, so that connection yields root. <sup><a href=\"#src-3\">[3]<\/a><\/sup><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What the attackers did<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Per THN&#8217;s account of F6&#8217;s investigation: <sup><a href=\"#src-2\">[2]<\/a><\/sup><\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>The attackers compromised two internet-facing Expressway devices.<\/li>\n\n<li>Through one of them, they reached two more cluster nodes on the internal network.<\/li>\n\n<li>They ran Python scripts, possibly AI-assisted according to THN, to scan for SMB services.<\/li>\n\n<li>They moved on to SQL Server and WinRM, and went after GitLab credentials.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">No attacker has been named.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Who is affected<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Expressway-C and Expressway-E, virtual and appliance, <strong>only when configured in a cluster<\/strong>, running X15.5.3 and earlier or X14 and earlier. <sup><a href=\"#src-1\">[1]<\/a><\/sup><\/li>\n\n<li>Standalone (non-clustered) Expressway nodes appear not to be affected, based on Cisco&#8217;s wording. <sup><a href=\"#src-1\">[1]<\/a><\/sup><\/li>\n\n<li><strong>Fix:<\/strong> upgrade to X15.5.20. Cisco lists no workaround. X14 and earlier have no fix in that train; migrate to a fixed release. <sup><a href=\"#src-1\">[1]<\/a><\/sup><\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Indicators<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">These come from F6 via secondary sources. No file hashes are public. <sup><a href=\"#src-2\">[2]<\/a><\/sup><sup><a href=\"#src-3\">[3]<\/a><\/sup><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>IP addresses: 66.179.31[.]32 and 18.130.47[.]116<\/li>\n\n<li>Log entry: <code>wombat@127.0.0.1<\/code> in the Erlang system log (<code>erlang.log<\/code>)<\/li>\n\n<li>Files: Python scripts in paths like <code>\/mnt\/harddisk\/i1234\/<\/code> or <code>\/mnt\/harddisk\/i1234a\/<\/code><\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">How to check your devices<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Cisco publishes no compromise checks. These read-only commands come from Ostorlab and were <strong>not tested by MAG212<\/strong>. Run them only on devices you administer. <sup><a href=\"#src-3\">[3]<\/a><\/sup><\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>grep -R &quot;wombat@127.0.0.1&quot; \/var\/log\/ 2&gt;\/dev\/null<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-code\"><code>find \/mnt\/harddisk -maxdepth 3 -type f -name &#x27;*.py&#x27; 2&gt;\/dev\/null | grep -E &#x27;\/i[0-9]{4}[A-Za-z]?\/&#x27;<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">From a network that is not a cluster peer, this should fail:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>nc -vz expressway.example.com 4372<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Any hit means incident response. Rebuild from known-good images and rotate credentials the device could reach.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What to do now<\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Upgrade every cluster node to X15.5.20 or migrate off X14. <sup><a href=\"#src-1\">[1]<\/a><\/sup><\/li>\n\n<li>Allow TCP 4371 and 4372 only between cluster peers. Neither Cisco nor F6 says this explicitly; it follows from where the bug lives. <em>(MAG212 analysis)<\/em><\/li>\n\n<li>Hunt for the indicators above, and check firewall logs for the two IP addresses.<\/li>\n\n<li>If a device was exposed, review SQL Server, WinRM and GitLab access from it.<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\">Related on MAG212 CYBER<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><a href=\"https:\/\/cyber.mag212.com\/the-keys-to-vsphere-mag212-cyber-daily-november-20-2026\/\">MAG212 CYBER Daily, 20 November 2026: The keys to vSphere<\/a> (full issue and PDF)<\/li>\n\n<li><a href=\"https:\/\/cyber.mag212.com\/a-ten-year-old-counter-mag212-cyber-daily-november-19-2026\/\">MAG212 CYBER Daily, 19 November 2026: A ten-year-old counter<\/a><\/li>\n\n<li><a href=\"https:\/\/cyber.mag212.com\/one-equals-sign-too-many-mag212-cyber-daily-november-18-2026\/\">MAG212 CYBER Daily, 18 November 2026: One equals sign too many<\/a><\/li>\n\n<li><a href=\"https:\/\/cyber.mag212.com\/the-keys-were-already-inside-mag212-cyber-weekly-november-14-2026\/\">MAG212 CYBER Weekly, 14 November 2026<\/a><\/li>\n\n<li><a href=\"https:\/\/cyber.mag212.com\/subscribe-free\/\">Subscribe free to MAG212 CYBER<\/a><\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Sources<\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n<li><span id=\"src-1\">[1]<\/span> Cisco, &#8220;<a href=\"https:\/\/sec.cloudapps.cisco.com\/security\/center\/content\/CiscoSecurityAdvisory\/cisco-sa-vcs-static-cred-hr7EWZ8t\" rel=\"noopener\" target=\"_blank\">cisco-sa-vcs-static-cred-hr7EWZ8t: Expressway static credential vulnerability<\/a>&#8220;, 21 Oct 2026.<\/li>\n\n<li><span id=\"src-2\">[2]<\/span> The Hacker News, &#8220;<a href=\"https:\/\/thehackernews.com\/2026\/11\/hackers-exploit-critical-cisco.html\" rel=\"noopener\" target=\"_blank\">Hackers exploit critical Cisco Expressway flaw<\/a>&#8220;, 19 Nov 2026.<\/li>\n\n<li><span id=\"src-3\">[3]<\/span> Ostorlab, &#8220;<a href=\"https:\/\/blog.ostorlab.co\/cisco-expressway-root-rce-cve-2026-76466.html\" rel=\"noopener\" target=\"_blank\">Cisco Expressway root RCE CVE-2026-76466<\/a>&#8220;, 19 Nov 2026.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\"><em>Written and edited by El Mostafa Ouchen for MAG212 CYBER. Facts checked against the sources above as of 20 November 2026, 6:00 AM PT.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Cisco a corrig\u00e9 la vuln\u00e9rabilit\u00e9 CVE-2026-76466 en octobre\u00a0: les p\u00e9riph\u00e9riques Expressway en cluster acceptaient des identifiants cod\u00e9s en dur permettant d'obtenir les privil\u00e8ges root. La soci\u00e9t\u00e9 de s\u00e9curit\u00e9 F6 signale d\u00e9sormais que des attaquants ont exploit\u00e9 cette faille pour compromettre quatre \u00e9quipements au sein d'une organisation russe. Qui est concern\u00e9\u00a0? Comment cela fonctionne-t-il\u00a0? Quel est le correctif\u00a0? Quels sont les indicateurs et les commandes de recherche\u00a0?<\/p>","protected":false},"author":1,"featured_media":4453,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[19,13],"tags":[309,504,505,513,512,514,417],"class_list":["post-4455","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-critical-cves","category-cyber-incidents","tag-cisco","tag-cisco-expressway","tag-cve-2026-76466","tag-erlang","tag-hard-coded-credentials","tag-unified-communications","tag-vulnerability-management"],"_links":{"self":[{"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/posts\/4455","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/comments?post=4455"}],"version-history":[{"count":0,"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/posts\/4455\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/media\/4453"}],"wp:attachment":[{"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/media?parent=4455"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/categories?post=4455"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/tags?post=4455"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}