On this page (7 sections)
A critical flaw has been published for the PLANET GS-5220-8P2T2S managed switch (hardware version 3.0). According to the NVD record, firmware versions before 3.2412b261008 contain a stack-based buffer overflow that an unauthenticated attacker can trigger by sending an oversized webstax_auth HTTP cookie to the device.
If you run this switch at an office, a hosting rack, a store or a client site, the web management interface is the part to worry about. The advisory describes memory corruption and potential denial of service. Whether it can lead to anything beyond that is not stated in the sources we reviewed.
What happened
The vulnerability was published on November 13, 2026 in the National Vulnerability Database and in the GitHub Advisory Database the same day, where the entry is marked as unreviewed. The GitHub entry lists three references: the NVD record, a PLANET security advisory and a VulnCheck advisory. We could not read the vendor or VulnCheck pages, so the details here come from the CVE description only.
Only one independent publisher covers this so far. The NVD text repeats the same description, so it should not be treated as a second confirmation. Treat the technical details below as the current public picture, which may change once the vendor advisory is reviewed.
Technical details
A stack-based buffer overflow happens when a program copies data into a fixed-size memory area on the stack without checking that the data fits. Anything beyond the buffer spills over into neighboring memory, which can include the saved return address that tells the program where to continue running.
Per the CVE description, the switch's web service reads the webstax_auth cookie value and copies it into a fixed-size stack buffer with no length validation. A crafted unauthenticated request with an oversized cookie can overwrite the saved return address and corrupt stack memory. The stated result is memory corruption and potential denial of service.
The key point is that the cookie is processed before any login succeeds. The CVSS v4 metrics in the GitHub entry reflect this: network attack vector, low attack complexity, no privileges required and no user interaction, with high impact on confidentiality, integrity and availability of the vulnerable system. The description itself only names denial of service as the potential outcome, so do not assume more than that, but do not assume less either.
Who is affected
- Owners of the PLANET GS-5220-8P2T2S with hardware version 3.0 running firmware older than 3.2412b261008.
- Teams whose switch management web interface is reachable from the internet, a guest network, a shared VLAN or a flat office network.
- Agencies and hosting administrators who deployed this switch at client sites and may not track its firmware.
The sources do not say whether other PLANET models or other hardware revisions share the same code. Do not assume they are safe or affected; ask the vendor.
How to check your exposure
First confirm that you actually own the affected model and revision. The hardware version is normally printed on the device label, and the firmware version is shown in the switch's management interface. Compare it with 3.2412b261008.
Next, find out who can reach the management interface. The command below only tests whether the switch's web ports (80 and 443) accept connections and sends no malicious data. Replace the example address with your switch's management IP and run it from a Linux or macOS host with nmap installed, on a network segment that should not have management access. An "open" result means the interface is reachable from that segment.
nmap -p 80,443 192.0.2.10If you can reach it from the internet or from user and guest networks, treat that as the highest-priority exposure to close.
What to do now
- Identify every GS-5220-8P2T2S (hardware version 3.0) you manage and record its current firmware version.
- Open the PLANET security advisory (number 12 on the vendor's support site) and download the fixed firmware, 3.2412b261008 or later, directly from the vendor.
- Back up the switch configuration, then schedule a maintenance window to install the update.
- Restrict the management interface to a dedicated management VLAN or a short list of admin IP addresses, and never expose it to the internet.
- If you cannot patch immediately, block access to the switch's web interface at a firewall or with an access control list until you can.
- After updating, confirm the new firmware version in the interface and check that the switch's VLAN, port and PoE settings are intact.
- Review any logs or monitoring you have for unexpected switch reboots or management interface crashes since the vulnerability became public.
Detection and monitoring
Because the described impact includes denial of service, the most visible sign of attempts may be a switch that reboots or becomes unresponsive. Watch for unexplained restarts, management page timeouts and sudden loss of connectivity on the segments the switch serves. The sources do not describe specific log entries or indicators of compromise, so we cannot list any.
Keep a simple inventory of network gear with model, hardware revision and firmware version, and review it whenever new advisories appear. Uptime monitoring of the switch's management address, such as the checks described in Webforta Monitor, can help you notice outages quickly, though it will not tell you the cause.
What we do not know yet
- No source states whether the flaw is being exploited in the wild.
- The GitHub entry lists patched versions as unknown, so the fixed release is inferred from the affected range. Confirm it in the vendor advisory.
- The two scores differ because they come from different scoring systems: 9.8 in the CVE data and 9.3 under CVSS v4 in the GitHub entry. Both are rated critical.
- The sources do not say whether remote code execution is possible, only memory corruption and potential denial of service.
For broader guidance on keeping the systems around your websites in good shape, see our guide to small business website security.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
