CVE-2026-7273 — Zyxel GS1900 Series Switches Stack-Based Buffer Overflow Vulnerability
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, unauthenticated attacker to exploit the flaw and potentially execute OS commands via a crafted HTTP request.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- Confirmed exploitation (CISA KEV)+35
- EPSS 2.5% (30-day exploitation probability)+13
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
CISA required action CISA
Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
US federal deadline: Sep 24, 2026 — passed 21 day(s) ago
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Zyxel GS1900-10HP firmware, Zyxel GS1900-16 firmware, Zyxel GS1900-24 firmware…).
- Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Zyxel | GS1900-10HP firmware | version <= 2.90(AAZI.1)C0 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Zyxel | GS1900-10HP firmware | < 2.90\(aazi.2\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | GS1900-16 firmware | version <= 2.90(AAHJ.1)C0 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Zyxel | GS1900-16 firmware | < 2.90\(aahj.2\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | GS1900-24 firmware | version <= 2.90(AAHL.1)C0 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Zyxel | GS1900-24 firmware | < 2.90\(aahl.2\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | GS1900-24E firmware | version <= 2.90(AAHK.1)C0 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Zyxel | GS1900-24E firmware | < 2.90\(aahk.2\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | GS1900-24EP firmware | < 2.90\(abto.2\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | GS1900-24EP firmware | version <= 2.90(ABTO.1)C0 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Zyxel | GS1900-24HPv2 firmware | < 2.90\(abtp.2\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | GS1900-24HPv2 firmware | version <= 2.90(ABTP.1)C0 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Zyxel | GS1900-48 firmware | < 2.90\(aahn.2\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | GS1900-48 firmware | version <= 2.90(AAHN.1)C0 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Zyxel | GS1900-48HPv2 firmware | < 2.90\(abtq.2\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | GS1900-48HPv2 firmware | version <= 2.90(ABTQ.1)C0 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Zyxel | GS1900-8 firmware | < 2.90\(aahh.2\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | GS1900-8 firmware | version <= 2.90(AAHH.1)C0 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Zyxel | GS1900-8HP firmware | < 2.90\(aahi.2\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | GS1900-8HP firmware | version <= 2.90(AAHI.1)C0 | Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 8.8 | CVSS 3.1 | High | 2.8 | 5.9 | security@zyxel.com.tw via NIST National Vulnerability Database |
| 8.8 | CVSS 3.1 | High | — | — | GitHub, Inc. via GitHub Security Advisories |
| 8.8 | CVSS 3.1 | High | — | — | Zyxel via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (score shown at the top: security@zyxel.com.tw) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
CISA KEV details CISA
CISA lists a CVE once it has evidence of exploitation against real targets.
CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.
EPSS over time FIRST
Oct 12, 2026 → Oct 14, 2026 · 3 reading(s) · max 2.50%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
- Hunt retroactively in logs from before Sep 21, 2026 (KEV listing): exploitation may have started earlier.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · zyxel/gs1900-8 firmware, zyxel/gs1900-8hp firmware, zyxel/gs1900-10hp firmware, zyxel/gs1900-16 firmware, zyxel/gs1900-2
- Source status changed · Published → Analyzed
- Record published
- Affected products added · zyxel/gs1900-48hpv2 firmware, zyxel/gs1900-8 firmware, zyxel/gs1900-8hp firmware, zyxel/gs1900-10hp firmware, zyxel/gs19
- CVSS changed · 8.8
- Source status changed · → Published
- SSVC assessment updated
- Added to CISA KEV (detected)
- Record created in this database
- Added to CISA KEV catalog
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 13, 2026 – Oct 13, 2026
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
5 on the record
- www.zyxel.com/global/en/support/security-advisories/zyxel-security-advisory-for-sta
- nvd.nist.gov/vuln/detail/CVE-2026-7273
- www.greynoise.io/blog/open-season-on-kapibala-attacker-steals-government-records-wordp
- github.com/advisories/GHSA-rrv4-8jq5-8j78
- www.cisa.gov/known-exploited-vulnerabilities-catalog
Elsewhere on this site
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-7273 is "Zyxel GS1900 Series Switches Stack-Based Buffer Overflow Vulnerability", rated High. It affects GS1900-10HP firmware (Zyxel); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 8.8 describes technical severity. EPSS 2.50% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.