Zyxel GS1900 CVE-2026-107441: The Patch That Didn't Hold, and 996 Switches That Paid for It

In June, Zyxel patched a GS1900 switch flaw (CVE-2026-7273). But the fix didn't fully close it: Binarly found the exploit still worked, and GreyNoise saw data taken from around 996 switches in August. Zyxel reclassified the missing parameter-length validation as a new CVE, CVE-2026-107441, an out-of-bounds write giving unauthenticated root command execution. The real fix is 2.90 Patch 3.

3 min readIntermediate

Executive summary. CVE-2026-107441 is an out-of-bounds write in the CGI program of Zyxel GS1900 series managed switches that lets an unauthenticated attacker run OS commands as root via crafted HTTP requests. What makes it a case study is the backstory: Zyxel patched a related flaw (CVE-2026-7273) in June 2026, but that fix didn't fully close the hole. GreyNoise reported attackers took data from roughly 996 GS1900 switches around 17 August, and Binarly found the exploit still worked against all ten firmware builds that had received the June patch. Zyxel reclassified the missing parameter-length validation as a separate vulnerability, CVE-2026-107441, and shipped 2.90 Patch 3. If you "already patched this in June," you probably didn't.

Zyxel GS1900 patch-bypass timeline

What it is

Field Detail
CVE CVE-2026-107441 (bypasses the June fix for CVE-2026-7273)
Product Zyxel GS1900 series managed switches (10 models)
Weakness Out-of-bounds write in the switch CGI → unauth OS command exec
Privilege Commands run as root (Binarly)
Severity CVSS 8.8 vendor / 9.8 per Binarly
Fix 2.90 Patch 3 (advisory 3 Nov 2026)
Context ~996 switches breached ~17 Aug; tied to a China-nexus group

How it works

text
 Crafted HTTP request  ──►  GS1900 web CGI
          │   missing parameter-length validation
          ▼
 Out-of-bounds write in the CGI program
          │   (the June patch for CVE-2026-7273 didn't cover this path)
          ▼
 Unauthenticated OS command execution  ──►  root

The June fix addressed CVE-2026-7273, but a missing length check left an out-of-bounds write reachable without authentication. Binarly, investigating Red Heron infrastructure linked to the JITTERLY backdoor and SIXZUT rootkit, found the exploit still landed on patched firmware — so Zyxel issued a new CVE and a new patch (2.90 Patch 3).

Why it needs industry attention

Two reasons. First, network switches are blind spots: they rarely run EDR, rarely get firmware audits, and sit deep enough to enable traffic interception and lateral movement. Second, this is a patch-bypass — organizations that applied the June update are carrying a false sense of safety. The CISA KEV entry from September covers CVE-2026-7273, not the new CVE, so a KEV-driven program could easily miss it.

Fix and mitigation

  1. Install 2.90 Patch 3 on all 10 affected GS1900 models — this is the real fix, not the June update.
  2. Recheck firmware versions everywhere you "already patched" in June; confirm you're on Patch 3.
  3. Pull management interfaces off untrusted networks. The GS1900 web UI should never be internet-reachable.
  4. Assume compromise if exposed during the Aug–Oct window: inspect configs, firmware integrity, and for implants (JITTERLY/SIXZUT indicators).

How to detect it

  • Unexpected HTTP requests to the switch CGI from outside the management network.
  • Config or firmware changes you didn't make; integrity drift on switch firmware.
  • New traffic-mirroring or management sessions consistent with interception.
  • Device reachability from the internet — shodan-style exposure of the GS1900 web UI.

Conclusion

CVE-2026-107441 is a clean lesson that "patched" is a claim you have to verify. A length check missed in June became an unauthenticated root RCE that burned ~996 switches. Apply 2.90 Patch 3, re-verify firmware on every GS1900, and get switch management off the public internet.

Do this now: inventory GS1900 switches, install 2.90 Patch 3 on all 10 affected models, re-verify firmware where you only applied the June fix, and confirm no GS1900 web UI is internet-exposed.

Related: our network pentesting manual and the thread on the collapsing patch window.

Sources: BleepingComputer, SecurityWeek, The Hacker News, eSecurity Planet. Exploitation attribution per Binarly; confirm firmware details against Zyxel's advisory.

HackersRoot Research · Research team

The HackersRoot research team investigates attack techniques across AI systems, cloud and identity, and enterprise networks, then publishes the detections and hardening guidance that stop them.

More from HackersRoot →

Related research

Vulnerability Intel

FreeSWITCH CVE-2026-116779: One SIP Message to Command Execution

FreeSWITCH powers a huge share of the world's VoIP. A single crafted inbound SIP MESSAGE can select an 'api' chat protocol that the server then executes as FreeSWITCH API commands, several of which reach the operating system. The result is unauthenticated command execution, rated CVSS 9.8 and already exploited in the wild. Here's the mechanism, the fix in 1.11.3, and how to catch it.

Vulnerability Intel

OpenSSH 'SSHole' (CVE-2026-123158): When a Long Password Becomes a Skeleton Key

SSHole (CVE-2026-123158) is an OpenSSH authentication bypass on Linux systems that use musl libc without PAM. An oversized password makes the hash computation fail and return an asterisk, which matches the locked-account placeholder in the shadow file, so sshd accepts the login. It was exploited within about nine hours of disclosure. Here's the mechanism, who is affected, and the fix.

Vulnerability Intel

Oracle PeopleSoft CVE-2026-35273: An Unauthenticated Door Into the HR Mainframe of the Enterprise

Oracle issued an out-of-band alert for CVE-2026-35273, a missing-authentication flaw in PeopleSoft PeopleTools' Environment Management hub (PSEMHUB). Reachable over HTTP with no credentials, it can lead to server-side request forgery and remote code execution. Mandiant tied zero-day exploitation to ShinyHunters (UNC6240) against higher education. Here's the mechanism and the response.