Known exploited Network security
Zyxel GS1900: patch and check for intrusion
A switch update can close a vulnerability. It cannot tell you whether someone used the management interface before you installed it. For affected GS1900 owners, both questions need an answer.
- Vendor patches
- Available since June 16
- Authentication
- No login required PR:N
- CNA severity
- 8.8 CVSS v3.1
Zyxel rates the attack vector as adjacent network, AV:A. CISA lists September 24, 2026 as the FCEB remediation due date, alongside exposure evaluation and forensic-triage requirements. CVE record · CISA KEV
01 / The management interface
A crafted request can reach code that does not require a login
The vulnerability is a stack-based buffer overflow in the CGI program behind the switch's web-management interface. A crafted HTTP request can corrupt memory and potentially lead to operating-system command execution. The vendor identifies ten affected GS1900 models. Zyxel advisory
A strong administrator password does not repair this unauthenticated code path. Password hygiene still matters, but the immediate controls are fixed firmware and restricted access to management.
Do not turn the adjacent-network rating into an assumption that a particular deployment is safe. Review actual reachability from remote access, user, guest, and operational networks, as well as any internet exposure. FIRST's definition includes some restricted administrative domains and secure VPNs. CVSS attack-vector definition
Where a GS1900 connects a facility or an operational segment, include that dependency in the change plan. The concern is the switch's place in the network and the management access it exposes, not an assumed industrial-control capability.
02 / Public incident research
Configuration and credential exposure change the response
GreyNoise's September 21 public report describes theft from 996 switches in 48 countries on or about August 17. It reports 564 victims with factory-default credentials. Its analysis shows a collector retrieved through TFTP and data staged under the web directory for retrieval. These are the researcher's findings, not Deception Check fleet counts. Original public report, Zyxel section
The default-password figure does not establish how the exploit gained access. Likewise, a stolen password hash is sensitive evidence, but it is not proof of a recovered plaintext password or a subsequent login. Review affected secrets and any reuse without treating unobserved follow-on activity as a finding.
03 / Response plan
Keep the firmware work and the investigation connected
I would want the network and incident-response teams working from the same device list. The patch record should identify the exact switch and running build. The investigation should account for its management exposure and the evidence still available.
Close the vulnerable path
- Confirm model and build
- Install model-specific firmware
- Verify management restrictions
Account for prior access
- Preserve available records
- Review traffic and configuration
- Resolve findings and affected secrets
Keep the build verification, access checks, and triage outcome in one remediation record.
- Retain: permitted paths and access-test results
Restrict access while you assess the device
Allow management only from approved administration hosts. Enforce upstream controls where available. A management VLAN still needs access rules, especially when the switch itself is part of the boundary.
- Retain: original exports and collection record
Preserve what is available before disruptive recovery
Where practical, save relevant logs and a protected configuration copy before rebooting or resetting. Record device time, firmware, and collection times. Coordinate with incident response without leaving exposure open while waiting for a perfect evidence set.
- Retain: image source, running build, and service checks
Install and verify the appropriate update
Use the exact model's supported vendor image. Follow its upgrade instructions and confirm the running build afterward. Recheck management access and essential network services during the approved maintenance window.
- Retain: findings, recovery actions, and unresolved gaps
Investigate and complete recovery
Exposed, affected firmware warrants triage, not an automatic declaration of compromise. If evidence indicates intrusion, involve the vendor and incident-response team in restoring a trusted state. Rotate affected credentials through supported procedures after securing the device, including any reused secrets identified in the configuration.
04 / Match the complete build string
Model-specific fixed firmware
The June advisory lists the following fixes. In each row, the affected cutoff is the corresponding .1 build and earlier. Use the listed fix or a later vendor-confirmed fixed release for that exact model. Vendor patch table
| Model | Affected through | Listed fix |
|---|---|---|
| GS1900-8 | 2.90(AAHH.1)C0 | 2.90(AAHH.2)C0 |
| GS1900-8HP | 2.90(AAHI.1)C0 | 2.90(AAHI.2)C0 |
| GS1900-10HP | 2.90(AAZI.1)C0 | 2.90(AAZI.2)C0 |
| GS1900-16 | 2.90(AAHJ.1)C0 | 2.90(AAHJ.2)C0 |
| GS1900-24 | 2.90(AAHL.1)C0 | 2.90(AAHL.2)C0 |
| GS1900-24E | 2.90(AAHK.1)C0 | 2.90(AAHK.2)C0 |
| GS1900-24EP | 2.90(ABTO.1)C0 | 2.90(ABTO.2)C0 |
| GS1900-24HPv2 | 2.90(ABTP.1)C0 | 2.90(ABTP.2)C0 |
| GS1900-48 | 2.90(AAHN.1)C0 | 2.90(AAHN.2)C0 |
| GS1900-48HPv2 | 2.90(ABTQ.1)C0 | 2.90(ABTQ.2)C0 |
The letters identify the model's firmware branch. A version shown only as “2.90” does not establish whether the fix is installed. Check support status with Zyxel for older variants outside this table.
06 / Investigation leads
Look beyond failed logins
Build the review around approved administration and normal switch traffic. Start with the available evidence below. A missing log or an unmatched indicator is an evidence gap, not a clean bill of health.
Web-management requests
Review unusual CGI requests, repeated errors, and unexplained management access. Use any retained upstream logs or packet captures when the device's own records are limited.
Outbound connections
Investigate unexpected file transfers and destinations. Include TFTP, web traffic, and other protocols the device does not normally need. Compare timestamps with management requests.
Configuration and accounts
Compare with a trusted baseline. Investigate unexplained administration changes, accounts, VLAN membership, mirroring, or altered remote logging. These are review targets, not reported outcomes of this campaign.
Use published campaign indicators with their original context. A report covering several technologies can include artifacts from unrelated intrusions. Confirm applicability to the switch investigation before turning every listed domain, hash, or account into a GS1900-specific rule.
Close the item with evidence of the fix and a documented answer about prior access.
Sources and scope
- Zyxel security advisory and its official community copy: affected models, fixes, and June 16 publication.
- Zyxel CNA record: vulnerability description and severity vector.
- CISA KEV feed: inclusion, listed due date, and triage requirement. Federal teams should follow the linked BOD 26-04 and implementation guidance.
- GreyNoise public research, September 21: externally reported incident findings.
- FIRST CVSS v3.1 specification: interpretation of adjacent-network access.
Technical reference and review date
- Vulnerability
- CVE-2026-7273, CWE-121, stack-based buffer overflow in web-management CGI.
- CNA vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H- KEV review
- September 23, 2026. Forensic triage: Yes. Ransomware use: Unknown.
- First-party scope
- Two previously validated August 15 HTTP request records on different emulated interfaces. Related input abuse only. No new fleet-wide measurement or capture of this CVE is claimed.