Zyxel GS1900 Zero-Day CVE-2026-107441: Patch to .3 Firmware
Switches that already carried a vendor patch were still open to the attack that reached nearly 1,000 Zyxel GS1900 devices. The exploit used in that campaign hit a separate, unknown bug, not the one Zyxel fixed in June. This article covers what is publicly confirmed, what is still disputed, and what defenders should do first.
What happened
The story has two layers, and the second one is why it matters.
Layer one (June to September 2026). On June 16, 2026, Zyxel released fixes for CVE-2026-7273, a pre-authentication buffer overflow in the GS1900 series. Around August 17, GreyNoise saw a suspected Chinese-speaking actor it tracks as Kapibala exploiting these switches. GreyNoise reported 996 compromised devices across 48 countries. The attackers ran commands remotely, then pulled down a script that collected device configurations, hashed root credentials and network information. GreyNoise tied the activity to CVE-2026-7273. CISA added that CVE to its Known Exploited Vulnerabilities (KEV) catalog on September 21.
Layer two (September to November 2026). Binarly was investigating infrastructure linked to a threat actor it tracks as Red Heron, which is associated with the JITTERLY backdoor and SIXZUT rootkit. It found an exposed archive containing an obfuscated Python exploit for GS1900 switches. According to public reporting, the archive was named gs1900_bundle.tar.gz. Binarly found that the exploit still worked against firmware that already had the June fix. Binarly reported this to Zyxel on September 29, and Zyxel confirmed a new vulnerability on October 11. That flaw is now CVE-2026-107441.
Zyxel shipped firmware fixes on October 22. SecurityWeek gives October 23, so treat the exact day as minor reporting variance. Zyxel published its advisory on November 3, the same day Binarly published its findings (advisory BRLY-2026-057).
What is still unclear
- How many of the 996 switches fell to the new bug. GreyNoise's victim count was published under CVE-2026-7273. Reporting says it is unclear how many of those devices were compromised through CVE-2026-107441 specifically.
- Whether the bypass was deliberate. BleepingComputer notes the recovered exploit targeted firmware patched for CVE-2026-7273. It remains unclear whether the author built it to defeat those updates or hit a related flaw the earlier patch missed.
- Attribution. Public reporting names Kapibala (GreyNoise) for the mass exploitation and Red Heron (Binarly) for the infrastructure where the exploit was found. Public reporting reviewed here does not confirm that these are the same actor or that JITTERLY or SIXZUT were deployed on compromised switches. Treat both attributions as unconfirmed.
Who is affected
- Products: ten models in the Zyxel GS1900 series. Reporting names GS1900-8, GS1900-24 and GS1900-48 among them. Binarly's exploit targets MIPS-based units. The authoritative list is in Zyxel's November 3 advisory.
- Vulnerable firmware: builds in the form 2.90(xxxx.2)C0 and earlier. Fixed firmware: the model-specific 2.90(xxxx.3)C0 builds. The switches Zyxel patched in June (the .2 builds) are not safe.
- Scale: 996 switches in 48 countries were compromised, per GreyNoise, under the earlier CVE attribution. Of those, 564 reportedly still used factory-default credentials.
- Sectors and victims: public reporting does not name affected organizations or sectors. GS1900 units are smart-managed switches commonly found in small and mid-sized business and branch networks, but that is an inference about the product class, not a confirmed victim profile.
One severity detail is disputed. Zyxel's advisory describes a LAN-based, unauthenticated attacker and scores the flaw CVSS 8.8. Binarly says it works over ordinary HTTP from any network that can reach the switch, and rates it higher. The GreyNoise campaign spanning 48 countries is consistent with internet-reachable management interfaces, though reporting does not give exposure details.
How the attack works
CVE-2026-107441 is an out-of-bounds write in the CGI program of the GS1900 web management interface. Binarly says the exploit targets /cgi-bin/dispatcher.cgi. An unauthenticated attacker sends crafted HTTP requests, overwrites memory and gets OS command execution.
The bypass of the June fix is the interesting part. Reporting describes the June patch as adding a count check on request parameters. Binarly found the unsafe copy still runs before that check, so an attacker can corrupt the parameter counter first and slip past the validation. The same exploit reportedly worked unchanged against the June-patched builds.
After exploitation, GreyNoise's observations describe a simple post-exploitation flow: remote command execution, download of a collection script, then gathering of configs, hashed root credentials and network details. Publicly, this is a theft-and-reconnaissance flow. Reporting does not describe persistence mechanisms or lateral movement from the switches.
MITRE ATT&CK mapping
- T1190 – Exploit Public-Facing Application: crafted HTTP requests to the switch web interface.
- T1059.004 – Command and Scripting Interpreter: Unix Shell: OS command execution on the switch. This is inferred from the OS command execution described, not from a published shell transcript.
- T1105 – Ingress Tool Transfer: download of the collection script onto the device.
- T1602.002 – Data from Configuration Repository: Network Device Configuration Dump: theft of switch configurations.
- T1078.001 – Valid Accounts: Default Accounts: relevant as an exposure factor for the 564 switches with factory-default credentials. Reporting does not state that default logins were the entry vector.
Public IOCs and identifiers
- CVE-2026-107441 (this flaw, CVSS 8.8 per Zyxel). CVE-2026-7273 (the June flaw, in CISA KEV).
- Binarly advisory: BRLY-2026-057.
- Exploit archive name:
gs1900_bundle.tar.gz. - Targeted path:
/cgi-bin/dispatcher.cgi. - Related malware names (association unconfirmed on victim switches): JITTERLY, SIXZUT.
The sources reviewed do not list attacker IP addresses, file hashes, or the URL of the collection script. Anyone who needs network IOCs should check GreyNoise's and Binarly's original publications directly rather than rely on third-party summaries.
Detection guidance for defenders
Switches rarely run EDR, so detection depends on network-side telemetry: firewall, proxy, NetFlow, syslog and configuration backups. Email telemetry is not relevant here, because there is no phishing component in the reporting.
What to look for
- Inbound HTTP/HTTPS to switch management IPs from anywhere outside your admin network, especially requests to
/cgi-bin/dispatcher.cgi. - Unexpected outbound connections from switch IPs. A switch should talk to NTP, syslog, DNS and your management servers. A new outbound HTTP/HTTPS or other external connection could be the script download or data exfiltration.
- Configuration drift. Diff current running configs against known-good backups for new accounts, changed credentials, altered SNMP settings or changed management ACLs.
- Admin login anomalies from unfamiliar sources, particularly on units still using default credentials.
- Exposure scans. Check external attack-surface data for any GS1900 web interface answering on the internet.
Example hunting queries
Query 1 (KQL, assumes web or firewall logs in CommonSecurityLog and a watchlist of switch IPs):
let switches = _GetWatchlist('GS1900_Switch_IPs') | project SwitchIP;
CommonSecurityLog
| where TimeGenerated > ago(120d)
| where DestinationIP in (switches)
| where RequestURL has "/cgi-bin/dispatcher.cgi"
| where not(ipv4_is_private(SourceIP))
| summarize Requests=count(), FirstSeen=min(TimeGenerated), LastSeen=max(TimeGenerated) by SourceIP, DestinationIP, RequestMethod
| order by Requests desc
Finds external hosts sending requests to the vulnerable CGI endpoint on your switches; the 120-day window reaches back to the mid-August start of the campaign.
Query 2 (generic pseudo-query on flow or firewall logs):
SELECT src_ip, dest_ip, dest_port, SUM(bytes_out)
FROM firewall_or_netflow
WHERE src_ip IN (switch_management_ips)
AND dest_ip NOT IN (internal_ranges, approved_ntp, approved_syslog, approved_dns)
AND timestamp >= now() - 120d
GROUP BY src_ip, dest_ip, dest_port
ORDER BY SUM(bytes_out) DESC
Finds switches talking to external destinations they have no business reaching, which would fit the script download or config exfiltration stage.
Caveat: many deployments never log HTTP requests to switch management interfaces, and switch-side logs may be minimal. No request hit does not prove a clean device. If a switch was internet-reachable on a vulnerable build since mid-August, treat it as suspect and review its configuration regardless.
Mitigation and response
- Inventory every GS1900. Record model and firmware version. Do not assume a switch is fine because it was updated in June. Anything on a 2.90(xxxx.2)C0 build or earlier is vulnerable.
- Upgrade to the 2.90(xxxx.3)C0 build for each model. These are the October 22 fixes. Use the model-specific builds listed in Zyxel's advisory.
- Remove web management from the internet immediately. Restrict it to a dedicated admin VLAN or VPN with ACLs. This is the best compensating control if you cannot patch today.
- Replace default credentials on every unit. Reporting says 564 of the 996 compromised switches still used factory defaults.
- Triage exposed units as potentially compromised. For any switch that was internet-reachable or on a flat network with untrusted hosts since mid-August, compare its config to a known-good backup. Look for unknown accounts or changed settings.
- Rotate secrets that touched the device. Since attackers collected configurations and hashed root credentials, rotate admin and root passwords. Also rotate SNMP community strings, RADIUS or TACACS shared secrets, and any credentials stored in the config. Assume the hashes can be cracked offline, especially weak ones.
- Re-flash if integrity is in doubt. Public reporting does not describe persistence on these switches, so there is no confirmed clean-up procedure beyond patching and credential rotation. If you find unexplained changes, restore from known-good firmware and config, and treat the segment behind the switch as exposed.
- Update your tracking. If your vulnerability-management records show CVE-2026-7273 as remediated for these switches, add CVE-2026-107441 as a separate open item. Closing the KEV entry did not close this exposure.
What individuals should do
GS1900 units are small-business and prosumer-grade managed switches, so some home labs and small offices run them. If you own one, check the model and firmware in the switch's web UI, install the .3 firmware, change the default password, and make sure the management page is not exposed through port forwarding. Individuals who do not run these switches have no action to take.
FAQ
I patched for CVE-2026-7273 in June. Am I safe?
No. Binarly reports its recovered exploit works against the June-patched firmware, and Zyxel confirmed a separate flaw. You need the .3 builds released on October 22.
Were all 996 switches hit through CVE-2026-107441?
Not confirmed. GreyNoise's count was published under the earlier CVE. Public reporting does not say how many devices fell to the newer bug, though Binarly's finding suggests the attackers were not relying only on CVE-2026-7273.
Who is behind the attacks?
Attribution is unsettled. GreyNoise points to a suspected Chinese-speaking actor it calls Kapibala. Binarly found the exploit while examining Red Heron infrastructure. No public source reviewed confirms they are the same group, and the link between this campaign and JITTERLY or SIXZUT on victim switches is unconfirmed.
Bottom line
This is a high-priority patch for anyone running GS1900 switches. The flaw is unauthenticated command execution, it was exploited before a fix existed, and the vendor's earlier patch left the door open. Network infrastructure like this is rarely monitored, so the real risk is quiet credential and configuration theft that nobody notices. The unresolved questions on attribution and victim count do not change the response: upgrade to .3, take management interfaces off the internet, and rotate every secret the switch held.
Original reporting: BleepingComputer
Protect yourself with tools recommended by cybersecurity professionals:
The tools below are independently selected based on security audits, transparency, and real-world effectiveness.