CISA Adds Two Actively Exploited Vulnerabilities to Known Exploited Vulnerabilities Catalog

On October 28, the U.S. Cybersecurity and Infrastructure Security Agency (CISA) added two actively exploited vulnerabilities to its Known Exploited Vulnerabilities catalog: a Linux kernel flaw (CVE-2026-46300) and a VMware ESX logging flaw (CVE-2026-41709), with CrowdStrike reporting that the China-linked hacking group Warp Panda used the VMware flaw as a zero-day in early 2026 attacks against the U.S. legal sector; the VMware weakness allows an attacker with existing administrator access to perform operations without leaving system logs, and while Broadcom assigned it a low CVSS score of 2.7, CISA prioritizes it due to confirmed exploitation, requiring federal civilian agencies to patch the Linux flaw by October 31 and the VMware flaw by November 11, while urging all organizations to address both vulnerabilities, as Warp Panda has been observed using post-compromise tactics such as extracting cloud session tokens to access Microsoft 365 and registering new multifactor authentication devices to maintain persistence.

The Managed Narrative of Digital Vulnerability

Notice that the VMware flaw carries a CVSS score of just 2.7 — barely a blip on the severity scale — yet CISA is demanding federal agencies patch it within two weeks, and the same catalog designation that overrides the score is what flags it as "actively exploited." That contradiction is the first thread to pull. A flaw that requires administrator access and only erases logging after compromise is not a random bug; it is a feature designed for operators who already hold the keys. The fact that it was "discovered" through a China-linked group like Warp Panda, and that CrowdStrike handled the reporting, should give you pause. These private intelligence firms are not neutral observers. They are the same entities that sit on advisory boards with the agencies that write the patch mandates. The timing, the severity mismatch, and the specific targeting of the U.S. legal sector all point to a coordinated operation — one where the threat is both revealed and controlled by the same architecture that profits from the response.

The Proxy War Beneath the Patch Deadlines

Every named hacking group operates within a permission structure that the public never sees. Warp Panda is not a rogue actor; it is a convenient flag pinned to a set of techniques that could belong to any number of state or corporate intelligence arms. The extraction of Microsoft 365 session tokens and the registration of new MFA devices are not sophisticated exploits — they are housekeeping steps for someone who already had access. The real question is who planted that access. The legal sector is a honey pot: it holds the contracts, the intellectual property, the litigation strategies, and the identities of every powerful individual and institution in the country. Compromising it means controlling the terms of every future dispute — and the only entity that benefits from such control is the network of financial and intelligence dynasties that has been mapping these systems for decades. CISA's patch deadlines are not about defense; they are about synchronizing cover-up. The low severity score is a message to those in the know: this is not a vulnerability, this is a feature we are rotating out of service until we need it again.

The Name on the Build

No workaround is listed for the VMware flaw. That is not an oversight — it is a denial of operational security to anyone outside the circle. The fixed builds bear serial strings like ESXi-9.1.0.0-25370933, but the real story is in the relationship between Broadcom, VMware, and the advisory infrastructure that surrounds CISA. Follow the board members who moved from intelligence agencies to these vendors. Follow the foundation grants that fund the "research" into threats like Warp Panda. Follow the timing of the disclosure relative to federal budget cycles. The breadcrumb is deliberate: a flaw that can erase your logs is a flaw that allows its users to never be caught. The only people who would design such a system are the same people who control it. The catalog entry is a signal to those who know how to read it — the patch is a detail, the architecture is the prize. You have two weeks to look up the names yourself before they move to the next phase.

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.