Threat researchCisent
Zyxel: the June patch didn't close the flaw being used against its switches
The exploit used against Zyxel GS1900 switches since August targeted a different flaw than everyone thought: the June patch didn't stop it, and the real fix came out on October 22.

On November 3, 2026, Zyxel published an advisory for a flaw in its GS1900 switches that lets an attacker on the local network run commands without credentials: CVE-2026-107441.1 That same day, security firm Binarly, which reported it, explained why it matters: it was the flaw the exploit used against these devices actually targeted, and the June patch didn’t close it.2
What happened
- June: Zyxel fixed a different GS1900 flaw, CVE-2026-7273.2
- August: according to GreyNoise, around August 17 a new exploit took data from 996 switches in 48 countries, including their configurations and hashed root credentials.3
- September: Binarly found that exploit in the JITTERLY malware’s infrastructure. On the 21st, GreyNoise tied it to the June flaw and CISA added that flaw to its catalog of exploited vulnerabilities. On the 28th, Binarly confirmed that the ten releases fixing the June flaw were still vulnerable: the exploit targeted another flaw.2
- October and November: Zyxel confirmed the new flaw on October 11 and released the fix on the 22nd.2 It published the advisory on November 3.1
According to Binarly, CISA’s alert protected no one from this attacker: anyone who updated to the June release stayed exposed.2
The flaw
- It’s an out-of-bounds write in the switch’s CGI program. Anyone on the local network, without credentials, can run operating system commands with a crafted HTTP request.1
- It affects ten GS1900 models, from the GS1900-8 to the GS1900-48HPv2. On the GS1900-8, for example, the vulnerable version is 2.90(AAHH.2)C0 and earlier, and the fixed one is 2.90(AAHH.3)C0.1
- Binarly believes the exploit was generated by a language model.2
What to do
- Update every GS1900 to its model’s fixed version, the one with “.3”,1 even if it already has the June patch: that patch doesn’t stop this exploit.2
- Keep the switches’ management out of reach of any machine on the network: the flaw is exploited from the local network and without credentials.1
- If a GS1900 was exposed, change its credentials and review its configuration: the exploit took both.3
- Don’t treat a device as protected just because its version says it’s patched. That’s Binarly’s conclusion: advisories and version numbers help, but they can’t be trusted blindly.2
Where Cisent comes in
With the GS1900, a switch with the June patch showed up as patched and was still open to the attack.2
Sentinel Red Team attacks the organization’s systems with its authorization and within the scope it defines, to find the gaps before an attacker does: the connected device running unsupported software, the admin panel reachable from outside, the vendor that manages it remotely. It’s ongoing testing, not one audit a year, and every new attack pattern helps train the defense.
Sources
Zyxel, “Zyxel security advisory for out-of-bounds write vulnerability in GS1900 series switches”, security advisory, November 3, 2026. https://www.zyxel.com/global/en/support/security-advisories/zyxel-security-advisory-for-out-of-bounds-write-vulnerability-in-gs1900-series-switches-11-03-2026↩︎
Fernando Mercês and Yegor Vasilenko, Binarly, “Pre-Auth RCE in Zyxel GS1900 Exploited in the Wild as a Zero-Day”, company blog, November 3, 2026. https://www.binarly.io/blog/zyxel-gs1900-rce-cve-2026-107441↩︎
GreyNoise, “GreyNoise Timeline: Kapibala Exploitation”, company timeline, accessed November 9, 2026. https://www.greynoise.io/chronicle/gntl-20260929-kapibala-exploitation↩︎