On this page (7 sections)
Zyxel GS1900 series switches that were updated in June to fix CVE-2026-7273 may still be open to unauthenticated command execution. According to Help Net Security, security firm Binarly found a ready-made exploit on the command and control server of an attacker, and that exploit still worked on all ten firmware releases carrying the June fix. It relies on a different flaw, now tracked as CVE-2026-107441.
If you run GS1900 switches in an office, a hosting rack or a store back room, this matters to you. A switch sits underneath everything else on the network, and a compromised one can expose configuration data and credentials even when your websites and servers are fully patched. Whether this specific exploit was used against real victims is not confirmed in the sources.
What happened
In June 2026 Zyxel published an advisory for CVE-2026-7273, a stack-based buffer overflow in the web management CGI of GS1900 switches. Patched firmware ended in .2 (for example 2.90(AAHH.2)C0 for the GS1900-8). Zyxel credited researchers from ISCAS for reporting it.
On September 21, CISA added CVE-2026-7273 to its Known Exploited Vulnerabilities catalog, with a due date of September 24 for US federal agencies and a forensic triage requirement. Help Net Security reports that GreyNoise had observed a Chinese-speaking threat actor exploiting that flaw to pull configuration data, networking information and hashed root-level credentials from nearly 1,000 devices across 48 countries.
Days before that report, Binarly was examining malware tied to the same actor. Per Help Net Security, an open directory on the attacker's command and control server held a ready-made exploit for the GS1900 web management CGI. When Binarly tested it, the exploit still achieved unauthenticated command execution on all ten firmware releases that already had Zyxel's June fix. Binarly told Zyxel on September 29, and Zyxel shipped a fix for CVE-2026-107441 on October 22. The CVE was published on November 3.
Technical details
Both flaws sit in the CGI program that serves the switch's web management interface, and both are described as allowing an unauthenticated attacker on the local network to potentially execute operating system commands through a crafted HTTP request. The difference is the bug class:
| CVE-2026-7273 | CVE-2026-107441 | |
|---|---|---|
| Weakness | CWE-121, stack-based buffer overflow | CWE-787, out-of-bounds write |
| CVSS | 8.8 (High) | 8.8 (High) |
| Attack vector | Adjacent / LAN-based | Adjacent / LAN-based |
| Authentication | None | None |
| Fixed by | 2.90 (XXXX.2)C0 builds (Zyxel advisory) | 2.90 Patch 3 builds (per Help Net Security; Zyxel's own advisory table was not in the research) |
| CISA KEV | Added 2026-09-21 | Not listed in the research |
The CVSS vector uses an adjacent attack vector, meaning the attacker needs access to the same network segment rather than a direct internet path. That lowers risk compared with an internet-facing flaw, but only if the management interface is not exposed more widely than you think.
Who is affected
Zyxel's June advisory for CVE-2026-7273 lists ten models: GS1900-8, 8HP, 10HP, 16, 24, 24E, 24EP, 24HPv2, 48 and 48HPv2. Those ten come from that earlier advisory, not from the CVE-2026-107441 one. Help Net Security says Binarly's exploit worked on all ten firmware releases that carried the June fix, and that any GS1900 on a 2.90 Patch 2 build (XXXX.2)C0 or earlier is vulnerable.
The full list of models and versions affected by CVE-2026-107441 was not in the research. The CVE record names the GS1900-24E explicitly, so check Zyxel's advisory for CVE-2026-107441 for the exact model and firmware table.
Realistic exposure is highest where the switch management interface is reachable from untrusted segments: flat office networks, shared hosting or colocation VLANs, guest Wi-Fi bridged into the same network, or any switch whose web interface was published to the internet.
How to check your exposure
- List every Zyxel GS1900 switch you own, including ones in closets, branch offices and client sites.
- Log in to each switch's management interface and note the model and firmware version shown there.
- Compare the version with Zyxel's advisories for CVE-2026-7273 and CVE-2026-107441. Per Help Net Security, anything on a 2.90 (XXXX.2)C0 build or earlier needs the Patch 3 release.
- Check which networks can reach each switch's web management port, and whether it is reachable from the internet.
What to do now
- Obtain the fixed firmware for each GS1900 model from Zyxel as described in its advisory, confirm availability for your model there, and upgrade every affected switch.
- Do not assume a switch is safe because it carries the June (XXXX.2)C0 firmware.
- Restrict the web management interface to a dedicated management VLAN or specific admin addresses.
- Make sure no GS1900 management interface is reachable from the internet.
- As a precaution, change administrator passwords after upgrading; GreyNoise reportedly saw hashed root-level credentials taken in the CVE-2026-7273 attacks.
- Review switch configuration for unexpected changes and look for unfamiliar admin accounts or settings.
- Check network logs for unusual HTTP requests to the switch management address, especially from other internal hosts.
- If you find signs of compromise, treat connected credentials as exposed and follow your incident process.
Detection and monitoring
CISA's entry for CVE-2026-7273 says forensic triage is required, and Help Net Security advises administrators to look for evidence of compromise. Exploitation of a switch may leave little on the websites behind it, so focus on the network side: configuration exports compared against a known-good copy, admin login history, and traffic from the switch to unfamiliar external addresses.
For the sites and servers on the same network, watch for unexpected changes to DNS records and TLS certificates, which can be early signs that something upstream has been tampered with. Webforta Monitor tracks certificate, DNS and header changes, and the free SSL checker lets you spot-check a certificate by hand. For broader guidance, see what to do if a website is hacked.
The lesson for patch management
Binarly's researchers said advisories and version numbers help but cannot be blindly trusted, and argued for checking binary code directly. Few site owners can do that, but the practical takeaway is simple: a fixed version number tells you a named CVE was addressed, not that the same component is free of similar bugs. Prioritize devices that expose an unauthenticated web interface, keep them off untrusted networks, and re-check vendor advisories after any exploited-in-the-wild report.
Binarly also said it believes the exploit was generated with an LLM. That is Binarly's belief, not a confirmed fact.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
- CVE-2026-107441 - GitHub Advisory Database
- CVE-2026-7273 - GitHub Advisory Database
- Zyxel security advisory for stack-based buffer overflow vulnerability in GS1900 series switches | Zyxel Networks
- Known Exploited Vulnerabilities Catalog | CISA
- Patched Zyxel GS1900 switches remained open to in-the-wild exploit (CVE-2026-107441) - Help Net Security
