cve.bz

CVE-2026-7273 Zyxel GS1900 Series Switches Stack-Based Buffer Overflow Vulnerability

8.8 highKEVExploit referenceEPSS 2.7%

High (8.8) in Zyxel GS1900 Series Switches. In CISA KEV since 2026-09-21. EPSS 2.7% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
2.7% (unchanged from 2.7% a week ago; 2.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 86th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA KEV
listed 2026-09-21, due 2026-09-24
CISA's assessment (SSVC)
Exploitation: active · Automatable: no · Technical impact: total, assessed 2026-06-17. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-121 Stack-based Buffer Overflow
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-7273 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-7273?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-7273?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-7273 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-7273

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-7273](https://cve.bz/cve/badge/CVE-2026-7273.svg)](https://cve.bz/cve/CVE-2026-7273)

HTML:

<a href="https://cve.bz/cve/CVE-2026-7273"><img src="https://cve.bz/cve/badge/CVE-2026-7273.svg" alt="CVE-2026-7273"></a>

Affected

Versions

From the NVD's CPE matches.

ProductAffected
zyxel:gs1900-8_firmwarebefore 2.90\(aahh.2\)c0
zyxel:gs1900-8hp_firmwarebefore 2.90\(aahi.2\)c0
zyxel:gs1900-10hp_firmwarebefore 2.90\(aazi.2\)c0
zyxel:gs1900-16_firmwarebefore 2.90\(aahj.2\)c0
zyxel:gs1900-24_firmwarebefore 2.90\(aahl.2\)c0
zyxel:gs1900-24e_firmwarebefore 2.90\(aahk.2\)c0
zyxel:gs1900-24ep_firmwarebefore 2.90\(abto.2\)c0
zyxel:gs1900-24hpv2_firmwarebefore 2.90\(abtp.2\)c0
zyxel:gs1900-48_firmwarebefore 2.90\(aahn.2\)c0
zyxel:gs1900-48hpv2_firmwarebefore 2.90\(abtq.2\)c0

References

Check your stackJSON