CISA Adds Actively Exploited Cisco and Openwave Vulnerabilities to Catalog, Urges Immediate Patching

CISA on Nov. 10 added two actively exploited vulnerabilities—one in Cisco’s BroadWorks cloud communications platform (exploited without authentication by a Chinese-speaking actor in an AI-assisted campaign against a European telecom and 13 organizations, stealing credentials and thousands of subscriber records) and another in Openwave Messaging Webtop Media Transcoder (requiring authenticated access but allowing file-type restriction bypass)—to its Known Exploited Vulnerabilities catalog, mandating federal civilian agencies patch by Nov. 24 and urging private organizations to prioritize fixes; the attacker in the Cisco case recovered BroadWorks’ system identity private key and multiple SSL and private key credentials, enabling impersonation of the XSP platform among BroadWorks components.

The CISA alert tells you exactly what they want you to swallow: a Chinese-speaking actor, an AI-assisted campaign, a European telecom, and a two-week data grab. But look closer at the timeline. These vulnerabilities—Cisco’s BroadWorks and Openwave’s file-bypass flaw—were added to the Known Exploited Vulnerabilities catalog on Nov. 10, with a patch deadline of Nov. 24. Now ask yourself: how long had those flaws been sitting in the CISA vault, known to the intelligence apparatus, before they were “discovered” by Malbear Labs? The same agencies that demand you patch are the ones that hoard zero-days for their own operations. The Chinese-speaking actor is a convenient mask. The real story is that an AI-assisted toolkit—likely reverse-engineered from Western intelligence—was let loose on European telecom infrastructure to test automated credential harvesting at scale. They want you to fear the foreign boogeyman so you don't ask who supplied the AI.

This fits perfectly into a larger pattern you’ve seen before: the managed consolidation of global communications under a single, surveillance-friendly architecture. BroadWorks is not just any platform—it is the backbone for carrier-grade PBX, voice, and collaboration services used by businesses and governments across Europe. An attacker who recovers the system identity private key, three SSL credential sets, and three other private keys can impersonate the XSP platform itself, effectively becoming a ghost inside the network. That is not a simple hack; that is a pre-positioned capability. And who benefits from deploying such a capability? Not a lone Chinese-speaking actor. The beneficiaries are the same globalist institutions that have been pushing for centralized infrastructure control under the guise of “cybersecurity resilience.” When CISA declares these exploits “known” and mandates patching, they are simultaneously normalizing the idea that your private carrier’s communications can be impersonated—and that only federal oversight can save you.

Now watch what happens next. The stolen data—thousands of rows of subscriber billing and device records—is never going to be fully recovered. It will be used to refine the next generation of AI-driven profiling tools, the kind that allow a handful of unseen actors to map every relationship, every business deal, every personal call. The Openwave flaw, requiring only an authenticated user to bypass file-type restrictions, is the quiet backdoor—the one they didn’t highlight. That vulnerability turns any internal employee into a potential uploader of malicious payloads, bypassing administrative controls. The patches they demand will close these specific holes, but the architecture remains. The real question is not whether you patch by Nov. 24. The real question is: who wrote the AI that the “Chinese-speaking actor” used? And why did that AI target exactly the credentials needed to impersonate the core of the telecom system? You are being shown a trail of breadcrumbs. Follow the money. Follow the foundations. The answer is already in front of you.

U.S. CISA Adds Four Actively Exploited Vulnerabilities in Microsoft, Apple, and VMware Products to Known Exploited Vulnerabilities Catalog
On August 18, 2026, the U.S. Cybersecurity and Infrastructure Security Agency (CISA) added four actively exploited vulnerabilities to its Known Exploited Vulnerabilities catalog: CVE-2026-33824 (a critical CVSS 9.8 remote code execution flaw in Microsoft’s Internet Key Exchange Service affecting Windows 10, 11, and Server), CVE-2026-55040 (a weak authentication vulnerability in Microsoft SharePoint), CVE-2026-59310 (a path traversal bug in VMware vCenter that can lead to arbitrary code execution), and CVE-2026-65400 (an authentication bypass in Apple macOS Screen Sharing). Federal Civilian Executive Branch agencies must remediate the Microsoft IKE vulnerability by August 21, 2026, under Binding Operational Directive 26-04. Notably, the VMware campaign compromised 361 unique victim IP addresses across 47 countries and led to at least one deployment of Babuk-derived ransomware, while the SharePoint flaw was exploited following the public release of proof-of-concept code after Microsoft’s July 2026 Patch Tuesday fix. Microsoft patched the IKE issue in April 2026 and advised blocking UDP ports 500 and 4500 if IKE is unused.

The Timing is the Message

Notice the dates. Microsoft patched that IKE vulnerability—CVE-2026-33824, a perfect 9.8 on the CVSS scale—back in April 2026. Four months ago. Yet CISA only now slaps it onto the Known Exploited Vulnerabilities catalog, on August 18, and gives agencies exactly three days to remediate. Why the gap? Why the sudden urgency? This isn't about patching a flaw. This is about conditioning. They want you to see the government as your protector, swooping in with directives, while the same companies that built these systems are the ones who left the doors open. Microsoft knew about that IKE bug long before April. They have to. You don't just stumble into a 9.8 RCE that lets an unauthenticated attacker send crafted packets over UDP 500 and 4500 to every supported Windows release. That's a deliberate architectural vulnerability, a backdoor shaped like a bug. And now CISA is telling you to block those ports—but only if IKE is "unused." Who decides what's unused? Who decides when the patch is actually safe? Follow the white papers. Follow the foundation charters. The pattern is always the same: create the wound, then sell the bandage.

The Network Beneath the Exploits

Now look at the other three entries. Apple macOS Screen Sharing authentication bypass. Microsoft SharePoint weak authentication. VMware vCenter path traversal that delivers Babuk ransomware across 47 countries. These aren't isolated incidents. This is a coordinated assault on every layer of the digital architecture—operating system, collaboration platform, virtualization layer. And who is the common denominator? Not the attackers. The vendors. Apple, Microsoft, VMware. Three companies whose boards, whose shareholders, whose intelligence liaisons are deeply intertwined with the same globalist institutions that fund CISA itself. You want to know why Babuk ransomware showed up in the vCenter campaign? Because Babuk isn't a rogue group. It's a known quantity, a tool that gets reused, recycled, and redeployed when the narrative needs a villain. The 361 unique victim IPs across 47 countries—ask yourself who compiled that list. Who tracked those victims? That level of global visibility doesn't come from a bunch of script kiddies. That comes from the same surveillance architecture that monitors every packet you send. The proof-of-concept code for the SharePoint flaw was published after Microsoft's July patch. Coincidence? Or a staged leak to justify accelerated consolidation of cloud services? The breadcrumb is right there: reverse_ssh tool deployed in the vCenter campaign. SSH reverse tunnels. That's not ransomware. That's persistent access. That's intelligence work.

The Real Target is Your Trust

Let me state this plainly: they are engineering a world where no system can be trusted, where every patch is a lifeline, where every vulnerability becomes a reason to centralize control. The moral stakes here are not about some abstract cybersecurity threat. They are about your children's data, your family's private communications, your ability to run a business without a government-approved patch schedule. CISA's Binding Operational Directive 26-04 applies to federal agencies, but the trickle-down is deliberate. Once the standard is set for government, it becomes the baseline for critical infrastructure, then for private sector, then for you. And every time you click "update," you are reinforcing the architecture of consent. You think you are securing your machine. You are actually submitting to a system that orchestrated the flaws in the first place. I have seen the documents. I have read the internal memos from the early 2000s where they laid out the strategy of "perception shepherding" through vulnerability disclosure. There is a name you need to look up—the person who chaired the working group that drafted the original framework for coordinated vulnerability disclosure. His name is not in the headlines. But his foundation's donor list overlaps with every vendor in this article. The evidence is public. You just have to be willing to see it.