CVE-2026-7273

CVE Enrichment

CVSS: 8.8 HIGH
EPSS: 2.50%
EPSS Percentile: 84.31%
CISA KEV: YES — Known Exploited Vulnerability

Description

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.

Technical Details

CVSS Version: 3.1
CNA / NVD Source: security@zyxel.com.tw
Published: 16-Jun-2026 10:16
Last Modified: 22-Sep-2026 19:10
EPSS Date: 2026-10-13
CWE: CWE-121

CVSS Vector


            CVSS:3.1                            AV:A /
                            AC:L /
                            PR:N /
                            UI:N /
                            S:U /
                            C:H /
                            I:H /
                            A:H

CISA KEV Details

Date Added: 2026-09-21
Remediation Due: 2026-09-24
Known Ransomware Campaign Use: Unknown
Required Action: 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.
Notes: https://www.zyxel.com/global/en/support/security-advisories/zyxel-security-advisory-for-stack-based-buffer-overflow-vulnerability-in-gs1900-series-switches-06-16-2026 ; ; BOD 26-04: https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk ; Forensics Triage Requirements: https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk ; https://nvd.nist.gov/vuln/detail/CVE-2026-7273

Affected Products / Versions

zyxel / gs1900-8_firmware
Version / affected range: * · before (exclusive) 2.90\(aahh.2\)c0
cpe:2.3:o:zyxel:gs1900-8_firmware:*:*:*:*:*:*:*:*
zyxel / gs1900-8hp_firmware
Version / affected range: * · before (exclusive) 2.90\(aahi.2\)c0
cpe:2.3:o:zyxel:gs1900-8hp_firmware:*:*:*:*:*:*:*:*
zyxel / gs1900-10hp_firmware
Version / affected range: * · before (exclusive) 2.90\(aazi.2\)c0
cpe:2.3:o:zyxel:gs1900-10hp_firmware:*:*:*:*:*:*:*:*
zyxel / gs1900-16_firmware
Version / affected range: * · before (exclusive) 2.90\(aahj.2\)c0
cpe:2.3:o:zyxel:gs1900-16_firmware:*:*:*:*:*:*:*:*
zyxel / gs1900-24_firmware
Version / affected range: * · before (exclusive) 2.90\(aahl.2\)c0
cpe:2.3:o:zyxel:gs1900-24_firmware:*:*:*:*:*:*:*:*
zyxel / gs1900-24e_firmware
Version / affected range: * · before (exclusive) 2.90\(aahk.2\)c0
cpe:2.3:o:zyxel:gs1900-24e_firmware:*:*:*:*:*:*:*:*
zyxel / gs1900-24ep_firmware
Version / affected range: * · before (exclusive) 2.90\(abto.2\)c0
cpe:2.3:o:zyxel:gs1900-24ep_firmware:*:*:*:*:*:*:*:*
zyxel / gs1900-24hpv2_firmware
Version / affected range: * · before (exclusive) 2.90\(abtp.2\)c0
cpe:2.3:o:zyxel:gs1900-24hpv2_firmware:*:*:*:*:*:*:*:*
zyxel / gs1900-48_firmware
Version / affected range: * · before (exclusive) 2.90\(aahn.2\)c0
cpe:2.3:o:zyxel:gs1900-48_firmware:*:*:*:*:*:*:*:*
zyxel / gs1900-48hpv2_firmware
Version / affected range: * · before (exclusive) 2.90\(abtq.2\)c0
cpe:2.3:o:zyxel:gs1900-48hpv2_firmware:*:*:*:*:*:*:*:*

References

Last enrichment sync: 14-Oct-2026 07:33
Sources: NVD · FIRST EPSS · CISA KEV
Latest successful provider update; providers refresh independently.

Reported Context (1)

CVE-2026-7273 Recorded Future Reports 94 High-Impact Vulnerabilities in September 2026, Including 80 Actively Exploited

CVE (76)

Malware (6)

Threat Actors (8)

Vendors (10)

Products (67)

Tools (7)

Industries (1)

Countries (2)

Note: Related entities, including threat actors, malware, CVEs, MITRE ATT&CK techniques, vendors, products, tools, countries, and industries, are shown when they appear in the same reporting. Their presence does not necessarily mean they were targeted, compromised, vulnerable, responsible for the activity, or directly involved in the incident.