Skip to content
Venture Capital

What GreyNoise Counted: 996 Zyxel GS1900 Switches Compromised After a June Patch

Zyxel's June GS1900 switch fix was followed by a second flaw in the same CGI code, with 996 devices compromised across 48 countries, per GreyNoise.

Dark illustration of a Zyxel GS1900 switch under a shield icon, with labels for a zero-day flaw and a failed earlier patch

Zyxel released a firmware fix for a flaw in its GS1900 series network switches in June 2026. By late September, a campaign against those switches had compromised 996 devices in 48 countries, according to GreyNoise. The attackers collected device configurations, hashed root credentials and network details. A second flaw, which Zyxel's November advisory gives its own CVE number, was reported to work against firmware that already carried the June fix.

The record runs from a June advisory to a November one. The reports differ on some firmware dates and on the device count, and those differences are set out below.

What the June Fix Covered

The first flaw is CVE-2026-7273, a stack-based buffer overflow in the CGI program of GS1900 firmware. Zyxel's advisory, first released on June 16, 2026, says a LAN-based attacker who needs no login could send a crafted HTTP request to potentially run operating system commands. The advisory gives no CVSS score.

Ten models were covered: the GS1900-8, -8HP, -10HP, -16, -24, -24E, -24EP, -24HPv2, -48 and -48HPv2. Each has its own build string. For the GS1900-24, the affected build was 2.90(AAHL .1)C0 and the fixed build was 2.90(AAHL .2)C0. The advisory describes no workaround and advises users to install the patches. The advisory credits researchers from ISCAS with reporting the issue.

The June advisory therefore treated builds ending in .1 and earlier as affected, and .2 as fixed, for this flaw. The November advisory moves that line.

How the Campaign Ran Against Switches

Help Net Security reports that GreyNoise says a Chinese-speaking threat actor carried out the attacks, which happened on or about August 17.

The threat actor took device configurations, hashed root credentials and networking information. Help Net Security reports that GreyNoise recorded 564 victims with factory default credentials.

GreyNoise counted 996 compromised switches across 48 countries. Help Net Security says the affected switches are predominantly located in Italy, the US, Taiwan, South Korea and a number of EU countries.

On September 21, CISA added CVE-2026-7273 to its Known Exploited Vulnerabilities catalog, with a September 24 deadline for US civilian federal agencies to address it.

BleepingComputer reports that GreyNoise linked the actor to the Red Heron campaign, which Acronis had reported earlier.

The Second Flaw Behind the June Build

According to BleepingComputer, Binarly found that the exploit still worked against firmware patched for CVE-2026-7273; whether it was built to bypass those patches or to target a related flaw they missed is unresolved. Zyxel's November 3 advisory acknowledges Yegor Vasilenko of Binarly and lists the new bug as CVE-2026-107441.

The new flaw is an out-of-bounds write in the same CGI program. Zyxel describes the same route as the earlier one: a LAN-based, unauthenticated attacker using a crafted HTTP request to potentially execute OS commands. BleepingComputer places the flaw in the GS1900 web management interface. The advisory gives no CWE or CVSS score.

The November advisory lists builds ending in .2, the ones that carried the June fix, as affected. The fixed builds end in .3 for each of the ten models. In the GS1900-24 example, the affected build is now 2.90(AAHL .2)C0 and earlier, with 2.90(AAHL .3)C0 as the fix.

The advisory states no workaround and says nothing about the flaw being exploited in the wild. It says patches cover models still within their vulnerability support period, and that models not listed are unaffected.

Where the Timeline and Counts Differ

The firmware date and the advisory date are different events, not a conflict. BleepingComputer says Zyxel released the firmware updates on October 22, 2026, and published its advisory on November 3. Zyxel's advisory lists November 3 as its initial release and gives no separate release date for the new builds.

The device count also appears in two forms. BleepingComputer's headline says nearly 1,000 switches, while its text gives 996 devices, per GreyNoise. Help Net Security also gives 996 devices.

The CVE behind the attacks is also described differently. Help Net Security's September headline names CVE-2026-7273 alone. BleepingComputer's November report says GreyNoise first attributed the campaign to CVE-2026-7273, and it names both numbers.

Neither Zyxel advisory gives a CVSS score.

“The June fix covered one flaw, and the November advisory lists the June builds as still affected.”

What the Build Tables Show for Network Buyers

Each advisory names models and build numbers, and each moves the affected range. The advisory date and the firmware date are separate facts, and the table in each advisory is where the affected and fixed builds are stated.

The two advisories differ in scope. The June advisory treated builds ending in .1 and earlier as affected. The November advisory treats builds ending in .2 and earlier as affected, and names the .3 builds as fixes. Both say that models not listed are unaffected.

Across the same ten entries, the affected column moves from .1 to .2, and the fixed column moves from .2 to .3. A reader comparing the two tables will see that the June fix is listed as affected in November.

The Sequence From June to November

The sequence runs from a vendor fix in June, to a federal catalog entry in September, to a second vendor advisory in November. Each step is recorded in a different source, and some of the dates differ, as set out above.

Help Net Security and BleepingComputer each report the attack count, the country spread and the data taken. The Zyxel advisories cover the vendor and version details, and the Canadian Centre for Cyber Security notice covers the CISA catalog entry.


Related