Security Digest · Nov 3, 2026 · Vulnerability · Network edge
Zyxel GS1900 Zero-Day CVE-2026-107441 Beats June Patch
Exploited pre-auth RCE in Zyxel GS1900 switch web UI works on firmware patched for CVE-2026-7273. Upgrade to 2.90(xxxx.3)C0; urgent if management is reachable.
Our verdict
Patch this week
Every GS1900 still on a .2 or older build is open to the exploit used against roughly 1,000 switches, even if you patched in June. Upgrade to the .3 firmware this week, and today if switch management is reachable from the internet, a guest network or a flat LAN.
Who must act: Owners of GS1900-8, -8HP, -10HP, -16, -24, -24E, -24EP, -24HPv2, -48 or -48HPv2 switches on 2.90(xxxx.2)C0 or earlier, including those that applied the June 2026 CVE-2026-7273 fix.
Who can relax: Sites with no GS1900 switches, and sites on the .3 firmware whose switch web interface is reachable only from a locked-down management network.
- Affected
- GS1900-8 2.90(AAHH.2)C0 and earlier
GS1900-8HP 2.90(AAHI.2)C0 and earlier
GS1900-10HP 2.90(AAZI.2)C0 and earlier
GS1900-16 2.90(AAHJ.2)C0 and earlier
GS1900-24 2.90(AAHL.2)C0 and earlier
GS1900-24E 2.90(AAHK.2)C0 and earlier
GS1900-24EP 2.90(ABTO.2)C0 and earlier
GS1900-24HPv2 2.90(ABTP.2)C0 and earlier
GS1900-48 2.90(AAHN.2)C0 and earlier
GS1900-48HPv2 2.90(ABTQ.2)C0 and earlier - Fixed in
- GS1900-8 2.90(AAHH.3)C0
GS1900-8HP 2.90(AAHI.3)C0
GS1900-10HP 2.90(AAZI.3)C0
GS1900-16 2.90(AAHJ.3)C0
GS1900-24 2.90(AAHL.3)C0
GS1900-24E 2.90(AAHK.3)C0
GS1900-24EP 2.90(ABTO.3)C0
GS1900-24HPv2 2.90(ABTP.3)C0
GS1900-48 2.90(AAHN.3)C0
GS1900-48HPv2 2.90(ABTQ.3)C0 - CVSS
- 8.8 (v3.1, CNA)
- EPSS
- 2.8% (percentile 87)
- CISA KEV
- Yes, listed as known exploited
- Exploitation
- Exploited in the wild
- Severity
- High
What to do
- Inventory GS1900 switches and confirm each one's firmware build; anything ending .2 C0 or lower is vulnerable.
- Upgrade every unit to its 2.90(xxxx.3)C0 build (the 'V2.90 Patch 3' release).
- Remove any internet or guest-network path to switch management and keep the web interface on a management VLAN behind ACLs; verify with an external nmap scan.
- Change switch admin passwords, starting with any factory defaults, and rotate SNMP, RADIUS/TACACS+ and other secrets stored in configs.
- Treat any switch whose web interface was reachable from untrusted networks before the upgrade as possibly compromised and check it before trusting it.
How to check if you are affected or compromised
- Look for outbound connections from switch management addresses, especially TFTP (UDP 69) or other file transfers a switch should never initiate.
- Look for bursts of large POST requests to the switch's web interface or unexplained web-service crashes and reboots.
- Compare running configurations against a known-good backup for new accounts, changed passwords or altered management ACLs.
- If you suspect compromise, factory-reset the switch, flash the .3 firmware and restore a clean configuration rather than patching in place.
What happened#
On November 3, 2026, Zyxel published an advisory for CVE-2026-107441, an out-of-bounds write (CWE-787) in the CGI program of its GS1900 smart managed switches. According to the CVE record, it "could allow an unauthenticated adjacent attacker to exploit the flaw and potentially execute OS commands via a crafted HTTP request". Zyxel scores it CVSS 3.1 8.8 (AV:A/AC:L/PR:N/UI:N). Zyxel credits Yegor Vasilenko and Fernando Mercês of Binarly. The fixed firmware, "V2.90 Patch 3", was posted on Zyxel's community forum on October 23. Its release notes say only "Fixed Pre-authentication out-of-bounds write vulnerability."
The bigger news is the context. In September, roughly 1,000 GS1900 switches were reported compromised and the attacks were attributed to CVE-2026-7273. Zyxel had patched that bug in June, and CISA listed it in KEV. Binarly now says the attackers were actually exploiting this new flaw, so the June patch never stopped them. SecurityOnline summarizes Binarly's account. The researchers found an obfuscated Python script labeled "Zyxel GS1900 Pre-Auth RCE" in an open directory on a command server for the JITTERLY Linux backdoor. They tested it on real hardware, and it worked "without changes" against firmware that already carried the CVE-2026-7273 fix. SecurityWeek reports Binarly's conclusion that the flaw was exploited as a zero-day against almost 1,000 devices, and that "the patch for CVE-2026-7273 remained ineffective."
Binarly places the root cause in dispatcher.cgi. The program copies each POST parameter into a fixed global buffer without checking the parameter's size or the number of parameters. The June fix added checks "too late, after the parameter counter was already corrupted." The new firmware caps each copied field at 511 bytes and checks the count before copying.
Who is affected#
The same ten models as in June, on firmware up to and including the .2 builds that carried the June fix: GS1900-8, -8HP, -10HP, -16, -24, -24E, -24EP, -24HPv2, -48 and -48HPv2. The fixed builds end in .3 C0, for example 2.90(AAHL.3)C0 for the GS1900-24 and 2.90(ABTQ.3)C0 for the GS1900-48HPv2. The full table is in Zyxel's advisory and on NVD. Zyxel says on-market products not in the table are unaffected. The status of end-of-life GS1900 v1 hardware is not disclosed as of November 7, 2026.
Do you really need to act?#
If you own these switches, yes. Anyone who patched in June and moved on is still exposed to the exact exploit used in the wild. The adjacent-network rating still matters, though: the attacker needs HTTP or HTTPS access to the switch's web interface. If only a restricted management VLAN can reach it, the real risk is an attacker already inside that segment, and upgrading within the week is proportionate. If the web interface is reachable from the internet, a guest or tenant network, or a flat office LAN, treat it as urgent and assume the switch may already have been compromised. That is how the original campaign appears to have reached devices in dozens of countries.
As of November 7, 2026, CVE-2026-107441 is not in CISA's KEV catalog. CISA's SSVC entry in the CVE record, dated November 3, still lists exploitation as "none". The exploitation evidence comes from Binarly's analysis of the attacker's tooling, not from a vendor or government confirmation. No minimized public proof of concept had been released at the time of writing, though Binarly says it plans one.
What to do now#
- List every GS1900 and its firmware string from the web interface or your management system. Any build ending in .2 C0 or lower is vulnerable.
- Download the V2.90 Patch 3 firmware for each model and upgrade, for example from 2.90(AAHL.2)C0 to 2.90(AAHL.3)C0 on a GS1900-24.
- Check reachability from outside, for example
nmap -Pn -p 80,443 --open <your-public-ranges>, and from guest and user VLANs. Allow switch management only from an admin network. - Change admin passwords, starting with any factory defaults. Rotate SNMP communities and RADIUS/TACACS+ keys, since the earlier campaign stole configurations and password hashes.
- For switches that were exposed before the upgrade, follow the checks below before you trust them again.
How to tell if you were hit#
No hashes, IP addresses or domains for this exploit have been published as of November 7, 2026. Indicators published for the earlier CVE-2026-7273 campaign still apply, because Binarly says it was the same activity. Watch for outbound connections that a switch should never make, especially TFTP (UDP 69) from switch management addresses. Look for bursts of large POST requests to the web interface, crashes or reboots of the web service, and unknown hosts downloading files from the switch. Compare the running configuration with a known-good backup. If anything looks wrong, factory-reset the unit, flash the .3 firmware, restore a clean configuration and rotate every secret it held. Binarly ties the tooling to the JITTERLY backdoor and the SIXZUT rootkit, so in-place patching alone may not remove an implant.
Timeline#
- — Zyxel fixes CVE-2026-7273 in the .2 firmware builds.
- — CISA adds CVE-2026-7273 to KEV after reports of about 1,000 compromised switches.
- — Binarly reports the new flaw to Zyxel, according to SecurityWeek.
- — Zyxel posts the V2.90 Patch 3 (.3) firmware.
- — Zyxel advisory and CVE-2026-107441 are published, and Binarly publishes its findings.
- — The CVE is not in KEV, and no public proof of concept has been released.
Vulnerability records
- CVE-2026-107441 · An out-of-bounds write vulnerability in the CGI program of Zyxel GS1900-24E firmware versions through 2.90(AAHK.2)C0 could allow an unauthenticated adjacent…
- CVE-2026-7273 · KEV 2026-09-21 · A stack-based buffer overflow vulnerability in the CGI program of Zyxel GS1900-48HPv2 firmware versions through 2.90(ABTQ.1)C0 could allow a LAN-based…
Sources
Original sources first: vendor and project advisories, CVE and government records, the discoverers’ write-ups. Every claim above links to one of these. See how the Security Desk works.
Original and primary sources
- Zyxel — Security advisory for out-of-bounds write vulnerability in GS1900 series switches zyxel.com
- Zyxel Community — Switch GS1900 series V2.90 Patch 3 firmware release community.zyxel.com
- CVE record — CVE-2026-107441 cve.org
- NVD — CVE-2026-107441 nvd.nist.gov
- Binarly — New Zyxel GS1900 pre-auth RCE vulnerability revealed binarly.io
- Zyxel — Security advisory for stack-based buffer overflow vulnerability in GS1900 series switches (CVE-2026-7273) zyxel.com
- SecurityOnline — Zyxel GS1900 zero-day CVE-2026-107441 securityonline.info