Cisco Expressway CVE-2026-76466 (CVSS 9.8) Exploited and in CISA KEV: Hard-Coded Cluster Cookie Gives Unauthenticated Root, Attackers Pivoted to Internal Nodes — Upgrade to X15.5.20 by 23 November

Critical · 2026-11-21 · By H.A

Cisco Expressway CVE-2026-76466 (CVSS 9.8) Exploited and in CISA KEV: Hard-Coded Cluster Cookie Gives Unauthenticated Root, Attackers Pivoted to Internal Nodes — Upgrade to X15.5.20 by 23 November

A hard-coded cluster credential in clustered Cisco Expressway nodes is being exploited for unauthenticated root access after a public PoC, and CISA has added CVE-2026-76466 to KEV with a 23 November deadline and forensic triage required.

Overview

A critical flaw in clustered Cisco Expressway deployments is now being used in real attacks. Tracked as CVE-2026-76466 (CVSS 3.1 score 9.8, CWE-798), it lets an unauthenticated remote attacker run operating-system commands as root on Expressway-C (Core) and Expressway-E (Edge) nodes, on both virtual machines and appliances. CISA added it to the Known Exploited Vulnerabilities (KEV) catalog on 20 November 2026. US federal civilian agencies have until 23 November 2026 to act, and CISA has flagged the entry for forensic triage, which means agencies are expected to look for signs of compromise, not just patch.

The first confirmed intrusion followed a public proof-of-concept that appeared on GitHub about two weeks after Cisco's fix. Researchers investigating the case say the attackers broke into two internet-facing Expressway nodes and then used the cluster's own trust relationships to take over two more nodes inside the victim's internal network.

Expressway is the gateway many organisations use to connect Webex, Unified CM, remote and mobile workers, and outside video partners to internal collaboration systems. An Expressway-E node normally sits in the DMZ with one leg facing the internet, so a root-level compromise there is a direct route inside.

The Vulnerability

According to Cisco's advisory (cisco-sa-vcs-static-cred-hr7EWZ8t, bug ID CSCww27732), the flaw is in the Expressway database service that cluster peers use to synchronise with each other. Cisco gives two causes:

An attacker who holds the cookie and can reach the service can connect to it and call specific remote procedure call (RPC) commands that run arbitrary commands as root.

The public proof-of-concept says the service is the Erlang distribution listener on TCP 4372 (over TLS), and that a vendor maintenance identity and its matching cookie are hard-coded in the cluster-manager module, identical on every affected install. The author says they tested only Expressway-C X15.3.2 in a two-node cluster in "Permissive" mode, and did not test Enforcing mode, Expressway-E or X14. The advisory and the PoC describe the affected TLS mode differently, so do not treat any TLS setting as a safe configuration.

Key facts from the vendor:

Timeline

Tradecraft

The responders describe a short path from edge to core:

No one has attributed the attack to a named threat actor, and the victim has not been identified. Cisco has not published information on any further victims.

Indicators of Compromise

The researchers published these indicators (defanged):

No file hashes have been published.

Detection

grep -n "nodeup" erlang.log* | grep -i "wombat"
find /mnt/harddisk -maxdepth 2 -name "*.py" -newermt "2026-11-01" -ls

Recommended Actions

Analyst Assessment

The pattern is familiar: a hard-coded secret in an edge appliance, a fix with no workaround, and exploitation within days of a public PoC. Two details stand out here. First, the clustering requirement narrows the attack surface, but larger organisations, the most valuable targets, are the ones most likely to run Expressway in clusters. Second, cluster trust turns one exposed edge node into a bridge to internal nodes that were never reachable from the internet. Defenders who patch only the DMZ boxes and ignore the internal Expressway-C peers may leave attackers with a foothold.

The AI-assisted Python tooling fits a wider trend this month of attackers quickly building custom post-exploitation scripts. We expect more scanning for TCP 4372 now that the flaw is in KEV. Any organisation with clustered Expressway nodes still below X15.5.20 should assume it is being targeted and should hunt as well as patch.

Sources

COMPUTE NODE · · --:--:--

Fresh cybersecurity news,
daily threat intelligence.

Daily cyber news, live threat intel and exploited CVEs.

Everything in one place

Self-hosted, hardened, and yours.

RUN IT

Local AI console

Chat with a model on your own hardware via Ollama or any OpenAI-compatible server. No cloud, no key.

DEFEND

Cyber threat feed

Automatic daily intel from CISA KEV, NVD & GitHub advisories, a live cyber threat map, and your own notes.

NEWS

News & videos

Articles and updates on pentesting, AI, and cyber — with embedded video, including YouTube. Post your own.

DIRECTORY

Registry

Runtimes, models, MCP servers, agents, and a full security & pentest tooling section.

PUBLISH

Posts

Write, edit, publish, and share articles backed by a real database and your account.

COMMUNITY

Forum

Threads and replies across categories from Models to Hardware to Security.

CODE

Repos

Curated AI and security GitHub repos, plus a shelf for pinning your own.

DOWNLOAD

Skill packs

Agent starters, RAG scaffolds, and defensive security & VAPT report templates.

Registry

Runtimes, models, MCP servers, agent frameworks, and a security & pentest tooling section — all links out to the real projects.

Local AI console

Talk to a model running on your own machine through Ollama or an OpenAI-compatible server — your prompts and the model's replies always go straight from your browser to your local model, never through a Reef server. Attach files for context, and pick up saved chats where you left off.

Type /image a prompt in the box below to generate
Not connected

Local AI hardware benchmark

A spec-based compatibility advisor — tells you which local models your hardware can run well, which will be slow, and which to skip. Connect to Ollama below for a real, measured speed test instead of an estimate.

1. Your hardware

2. Live check against your local model server (optional)

If a local model server is running, this cross-references the table above with what you've actually got loaded — and runs a real, measured speed test instead of an estimate.

AI Database

A browsable catalog of AI models across providers — context windows, pricing, and capabilities.

Loading…

Cyber threat feed

Latest threats pulled automatically every day from CISA's Known-Exploited-Vulnerabilities catalog and NVD — plus threat intel you post yourself.

⇩ Export STIX
Loading threat feed…

Cyber threat map

Attacks happening right now, all over the world.

Connecting…
LIVE · MAURITIUS TIME--:--:--
attack route, country to country attack route into Mauritius attacker reported worldwide
Loading live data…
attackers reported per minute · click to rewindnow

Top attack routesweb

Attackers based inlast hour

Networkslast hour

Click any dot, feed row or table row to see that IP's profile.

Mauritius

Who attacks Mauritius

Loading…

Web attacks malicious requests to Mauritian websites that were blocked
Network DDoS floods meant to knock Mauritian servers offline

    Mauritius · last 24 h

    How Mauritius is attacked

    Network-level attacks (DDoS) aimed at Mauritius, by method. They try to knock servers and networks offline by sheer volume.

    • Loading…

    The ports or services these floods aimed at aren't published.

    Mauritius · last hour

    Attackers located in Mauritius

    0attackers located in Mauritius were reported in the last hour

    This counts attacks coming from Mauritius, not attacks on it: IPs in Mauritius that servers elsewhere reported for attacking them. Usually zero or one; when it rises, it's often a hacked local server or router.

    Worldwide today

    What attackers are knocking on

    Ports most targeted across a worldwide network of sensors .

    Worldwide today

    Most active attackers

    Ranked by how many separate sensors they hit. Click a row for its profile.

    IPCountryNetworkSensors hitReports
    What you're looking at
    Blue routes

    Share of attack traffic from one country to another. Thicker, faster streams carry more. Particles show volume, not one per attack.

    Every 15 min · published 1–2 h behind
    Amber flashes

    An attacking IP that servers around the world reported in the last minute, placed where the IP is. Its targets aren't published, so there's no line.

    Every minute · shown about 1 min behind
    Locations

    IP locations are approximate (city level at best) and show where the machine is hosted, not who controls it.

    Approximate · city level at best

    News

    Articles, guides and updates on pentesting, AI, and cybersecurity — with embedded video. Add your own, including YouTube.

    Loading…

    Posts

    Loading…

    Loading posts…

    Forum

    Questions, answers, and talk about running AI locally.

    Loading forum…

    GitHub repositories

    Curated AI and security repos, plus your own pinned shelf.

    Command board

    One-liners, configs, and advice worth keeping — shared by everyone here.

    ⚠ Commands are shared with all users. Never include credentials, tokens, or internal hostnames. Review anything before you run it.
    Loading commands…

    Skill packs

    Starter files served from the API — AI agent scaffolds plus defensive security & VAPT reporting templates. Click to download.

    Loading skills…

    Your watchlist

    Follow threat actors, malware, CVEs and vendors — we tell you when a new report, CVE record or exploitation alert mentions them.

    Threat Library

    Threat actors, malware and tools — their attack techniques, Reef Sentinel coverage and indicators of compromise.

    Loading…

    Threat Intelligence

    Curated threat write-ups, advisories and analysis — with cover media.

    Loading…

    Tutorials

    Step-by-step guides for running local AI, using the console, and tracking threats. Admins can add their own.

    Loading…

    Downloads

    Direct links to the official homepage/download page for well-known cybersecurity, penetration-testing, and local-AI software. Always verify checksums/signatures from the vendor before running anything.

    Loading…

    Privacy Policy

    Loading…

    Terms & Conditions

    Loading…

    Help & FAQ

    Answers to common questions about Reef Sentinel, plus a formatting guide for posts, articles, and comments.


    Formatting guide

    Commands you can type into the body of a post, comment, or reply — no HTML needed. Comments and short replies only support bold, italic, and inline code.

    Contact us

    Questions, feedback, or a security disclosure? Reach us directly, or send a message and we'll get back to you by email.

    Loading…

    Send a message

    VAPT Report Generator

    Build an engagement, add findings with a live CVSS calculator, and generate a branded, print-ready report.

    Recon Toolkit

    Investigate any domain, IP, URL, file hash, email or CVE in one search, plus breach and password checks, hash identification and a payload cheatsheet.

    Outage Monitor

    Is Microsoft 365, Facebook, Google, AWS or ChatGPT down? Live status of the big tech services from their official status pages, every incident with its full timeline, and how long each one took to fix.

    Website Checker

    Reads a website's HTTP response headers to identify its framework and server, shows any known CVEs for the exposed versions with details, and recommends what to do.

    Control panel

    Manage everything shown on the site — news & videos, posts, homepage headlines, and subscribers. Admin only.

    Overview
    Content
    Site
    Account & Security

    Email settings

    SMTP on ports 25/465/587 is blocked outbound by some hosts (e.g. DigitalOcean droplets by default) — Resend and Brevo send over their HTTPS API instead, so they work even then. Only the selected provider is used to send; the others stay saved but idle, so you can switch back any time without losing settings.

    Get a key from resend.com/api-keys. Uses the "From address" below as the sender — it must be on a domain you've verified with Resend.

    Get an API key (not an SMTP key) from app.brevo.com/settings/keys/api. Uses the "From address" below as the sender — it must be a verified sender in your Brevo account.

    "From address" and "Site name/URL" are shared by SMTP, Resend, and Brevo — they control what recipients see, regardless of which provider is active.

    Send a test email

    Sends through whichever provider is currently active above. Save your settings first if you just changed them.

    SIGNAL LOST

    We couldn't find this page

    The page may have been moved or deleted, or the address was mistyped.