CVE-2026-4795
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA missing authorization vulnerability in Zyxel GS1200-5v3 firmware versions through 1.00(ACPS.2)C0, GS1200-8v3 firmware versions through 1.00(ACPT.2)C0, GS1200-5HPv3 firmware versions through 1.00(ACPU.2)C0, GS1200-8HPv3 firmware versions through 1.00(ACPV.2)C0, and GS1200-10v3 firmware versions through 1.00(ACPW.2)C0 could allow a LAN-based, unauthenticated attacker to read the system configuration from a log file via a crafted HTTP request.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA missing authorization vulnerability in Zyxel GS1200-v3 series gigabit switches (GS1200-5v3, GS1200-8v3, GS1200-5HPv3, GS1200-8HPv3, GS1200-10v3) allows unauthenticated LAN attackers to read system configuration data from log files via specially crafted HTTP requests.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm device is Zyxel GS1200 seriesAccess the device web interface or check the device label/menu for the exact model number. Look for GS1200-5, GS1200-8, GS1200-8v2, GS1200-5HP, GS1200-8HP, or similar GS1200 variants.Affected if The device model number begins with GS1200 and is a Zyxel switch.
-
Verify web interface is enabledAttempt to access the device IP via HTTP/HTTPS on the typical management ports (typically 80 or 443). If a login page loads, the web interface is active.Affected if The web management interface is accessible and responds to HTTP/HTTPS requests.
-
Check if log endpoint accepts unauthenticated requestsUsing a tool like curl, send a crafted request to common log file paths such as /log or /cgi-bin/log?action=view without providing any authentication credentials. Observe if the response contains system configuration data or log content.Affected if The log endpoint returns sensitive configuration or log data without requiring login credentials.
-
Review network accessibility of management interfaceCheck if the device management IP is reachable from any network segment beyond the intended admin VLAN. Use ping and port scanning to confirm which IP addresses can reach the web interface.Affected if The management web interface is reachable from network segments other than the designated admin network.
A device is affected if it is a Zyxel GS1200 series switch with its web interface enabled and accessible, where the log viewing functionality can be reached without authentication credentials.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply vendor firmware updates when released; until then, restrict LAN access to trusted users only and consider network segmentation to limit exposure to this unauthenticated configuration disclosure.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-4795 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-4795 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data