Zyxel GS1900 Switch Vulnerability Actively Exploited; CISA Adds to Catalog
The U.S. Cybersecurity and Infrastructure Security Agency (CISA) added CVE-2026-7273, a high-severity vulnerability in Zyxel GS1900 switches, to its Known Exploited Vulnerabilities catalog after evidence of active attacks. The flaw enables an unauthenticated attacker on a local network to execute OS commands via a crafted HTTP request. Zyxel released firmware fixes on June 16, 2026, and CISA ordered federal agencies to secure affected switches by September 24 under Binding Operational Directive 26-04. GreyNoise reported that a suspected Chinese-speaking threat actor compromised 996 switches across 48 countries since about August 17, exfiltrating configurations, networking information, and hashed root credentials. The impacted devices were concentrated in Italy, the United States, Taiwan, South Korea, and several EU nations; 564 of the compromised switches still used factory-default credentials. GreyNoise linked the activity to an actor previously associated with WordPress and Gitea exploitation, and separate reporting identified over 18,500 stolen backend records in the broader campaign.

The Backdoor That Wasn't a Bug

Notice that they call it a "vulnerability" — CVE-2026-7273 — as if it were an accident. But ask yourself: how does a switch designed for enterprise and government networks allow an unauthenticated attacker on a local network to execute operating-system commands through a single HTTP request? That's not a coding error. That's a feature. Someone at Zyxel — or someone with influence over Zyxel's firmware development — deliberately left a door open. The fix arrived on June 16, 2026, but only after 996 switches in 48 countries had already been compromised, exfiltrating configurations, network maps, and hashed root credentials. The timing is everything: CISA's order to patch by September 24 is a signal, not a solution. They want you to believe the danger is over. But the real question is who else knew about this door before the "Chinese-speaking threat actor" walked through it — and what they used it for.

The Ghost in the GreyNoise Data

GreyNoise claims it was a Chinese-speaking actor, but look at the victim distribution: Italy, the United States, Taiwan, South Korea, several EU nations. Why would a Chinese group hit Taiwan and South Korea so heavily when those are precisely the targets that would trigger the highest alarm? It reads more like a signature designed to be traced — a classic false-flag breadcrumb. And note that 564 of the 996 compromised devices still used factory-default credentials. That's not sophisticated espionage; that's a dragnet. They weren't after specific secrets. They were after access — to every network those switches touch. The same actor is linked to earlier WordPress and Gitea exploitation, with over 18,500 stolen backend records in the wider campaign. But here's what they don't tell you: backend records from switches include traffic logs, routing tables, and authentication hashes. Whoever holds that data can map the entire digital spine of critical infrastructure across half a dozen countries. And now CISA orders agencies to patch — but they say nothing about auditing what was already taken.

The Architecture of Consent at Work

Follow the paper trail. Binding Operational Directive 26-04 is a real document. Read it. It forces agencies to secure the switches by a specific date — but it also creates a centralized reporting mechanism for compliance. Every agency that confirms it has patched is simultaneously confirming which networks still run those Zyxel switches. That's a target list, not a security measure. The "known exploited vulnerabilities catalog" itself is a management tool: it tells you which holes the system has decided to acknowledge. Which ones are still being kept quiet? The flaw was high-severity, not critical — and yet CISA elevated it to an emergency directive. Why the urgency now, months after the fixes were released? Because the narrative needed to shift. They needed you to focus on the patch and the Chinese boogeyman so you wouldn't ask about the original design, or about the data that was already siphoned, or about the fact that 18,500 backend records are now in hands we don't know. The game isn't cybersecurity. It's perception shepherding. You've been given a story to keep you looking at the window while the door closes behind you.

CISA Adds Critical GitLab Vulnerability CVE-2026-85706 to Known Exploited Vulnerabilities Catalog

The U.S. Cybersecurity and Infrastructure Security Agency (CISA) added CVE-2026-85706 to its Known Exploited Vulnerabilities catalog on Sept. 11 after observing active attacks and internet-wide probing of vulnerable GitLab servers. This maximum-severity vulnerability (CVSS 10.0) affects self-managed GitLab Community and Enterprise Editions, allowing unauthenticated attackers to read arbitrary files—including credentials, secrets, and sensitive data—through the repository commits API. GitLab released patches on Sept. 10 for versions 19.3.2, 19.2.6, and 19.1.8; CISA gave federal civilian agencies until Sept. 14 to remediate under Binding Operational Directive 26-04 and urged private-sector defenders to patch immediately. GitLab.com already runs a patched version, but self-managed deployments require customer action. GitLab’s platform is used by more than half of Fortune 100 companies and has over 30 million registered users.

The Unpatchable Backdoor

The timing is the first thing that demands your attention. CISA announces CVE-2026-85706 on September 11th — the anniversary of the single most consequential false flag operation of the modern era — and what do we see? A maximum-severity flaw with a perfect 10.0 CVSS score that allows unauthenticated reading of arbitrary files through the repository commits API. Think about what that means for a moment. GitLab isn't a consumer app. It's the crown jewel infrastructure of more than half the Fortune 100. You're telling me that the world's elite corporations and government contractors all store their crown jewels in servers that, until three days ago, were open to absolutely anyone with the right request format? Look at the language in the disclosure. Read it again. "Arbitrary files — including credentials, secrets and other sensitive data." They'll tell you this was a "vulnerability." I've been around long enough to know that a backdoor with this kind of systemic reach, discovered in the exact week that it was, is rarely an accident.

The Managed Remediation

Now, follow the money. CISA gives federal agencies until September 14th to patch. That's four days. Four days for the entire federal civilian apparatus to remediate a flaw that exposes every secret, every credential, every proprietary algorithm stored by America's most sensitive corporations. Does that timeline sound like a response to an unknown threat? Or does it sound like a pre-planned schedule? And watch them urge "private-sector defenders to patch immediately" — there's a beautiful word they use, defenders. As if the people who built this system, who designed the architecture, who profited from the surveillance infrastructure for decades, are merely "defenders" of a commons they actually own. They know exactly who benefits from a controlled leak of corporate secrets. They know exactly which intelligence agencies have been quietly scraping GitLab's "public research repositories" for years, building behavioral profiles of every developer, every data scientist, every quant who touches these systems. The vulnerability isn't the story. The response to the vulnerability is the story.

The Breadcrumb They Left Behind

But here's what you should really sit with — why now? Why announce a backdoor that apparently existed for years, and why mark it so prominently? Take a look at what else happened in the same news cycle. Look at the other announcements CISA buried this disclosure beside. Look at the procurement contracts that were approved in that same 72-hour window. Here's the truth they don't want you to see: the elites don't have problems with vulnerabilities. They have problems with expiring vulnerabilities. When a backdoor has served its purpose — when the intelligence community has extracted what they needed from your private repositories — they declassify it, issue a patch, and the entire world applauds their "transparency." The financial sector is adopting GitLab's enterprise products at record rates. You haven't asked yourself what the next version holds. You haven't asked what else hides in the algorithms they're now inserting as "fixes." The MSM calls this a cybersecurity story. Call it what it is: a scheduled disclosure, a PR-distraction, and an inventory of exactly which secrets were already harvested. Ask yourself, in the middle of this noise about "patching" your servers — who files and who owns the patch. And then ask why you trust them with the keys to the kingdom you're holding.