The images in this article were generated with artificial intelligence. How we publish
A critical vulnerability in several models of Zyxel routers and network devices has forced the company to publish security updates this month. The failure, recorded as CVE-2025-13942, allows the injection of commands through UPnP functionality, which at worst could give an attacker the ability to execute operating system orders on a computer without authentication.
According to Zyxel itself, the problem is in the processing of UPnP SOAP applications in a wide range of products, including CPE 4G LTE / 5G NR, CPE DSL / Ethernet, fiber ONT and wireless extenders. An attacker who sends manipulated UPnP messages could take advantage of this weakness to cause remote execution of commands on vulnerable devices; Zyxel explains in more detail the conditions and versions affected in his technical notice, available on his official website: Zyxel Security Advisory.

It is important to mitigate the real scope of the risk. For the operation to be remotely viable, two conditions are required: that UPnP is active in the device and that there is WAN access to the UPnP service. Zyxel indicates that the WAN access is deactivated by default in your equipment, so in many cases the practical exposure will be lower than that which suggests the theoretical severity of the failure. However, in networks where a supplier or user itself has activated remote access or UPnP, the danger is real.
Apart from this failure, Zyxel published corrections for two other high-gravity vulnerabilities that require valid credentials to be exploited: CVE-2025-13943 and CVE-2026-1459. Both would allow an attacker with authenticated access to run commands on the device system, so they also deserve immediate attention from responsible administrators and users.
The scale of the Zyxel ecosystem aggravates the situation: projects to track devices exposed to the Internet such as Shadowserver record almost 120,000 Zyxel teams of which more than 76,000 are routers. This presence is partly explained by the fact that many service providers deliver these equipment as "plug-and-play" when hiring a connection, with default configurations that do not always minimize the risk.
In addition, the United States Agency for Cyber Security and Infrastructure (CISA) maintains in its catalogue many Zyxel vulnerabilities that have been actively exploited. In your public register you can check the related entries and check which ones are listed as "well-known exploited": CISA Known Exploited Vulnerabilities.
Another point to be recalled is the management of the life cycle of the teams. Zyxel has recognized that certain old models will no longer receive patches for zero-state (zero-days) exploited vulnerabilities and has recommended that users replace these EOL (end-of-life) equipment with more recent alternatives that are updated. If the manufacturer does not provide correction for a device, the only real long-term defense is to replace the hardware with one with current support.
From a practical perspective, the first and most urgent recommendation is the usual in these cases: install firmware updates published by Zyxel as soon as possible. If you cannot update immediately, it is appropriate to check and, if appropriate, disable UPnP and remote access from the WAN in the computer configuration. It is also a good idea to change the default credentials, to segment the network to isolate the router of critical devices and, in business environments, to monitor traffic and logs by signs of unusual behavior.
If your modem or router provided it to you by your operator and you do not know how to access the management panel or apply the update, contact the supplier's technical service: many operators manage the updates remotely or can replace obsolete equipment. For business environments, where exposure can involve critical assets, it is worth having a response plan and reviewing inventory and hardware renewal policies.

The case of Zyxel illustrates a recurring lesson in the safety of domestic networks and small businesses: devices widely deployed and configured by default become priority targets for attackers. Although not all users will be at immediate risk for operating conditions, the public availability of these failures and the number of devices exposed justify a proactive reaction.
For those who want to consult the primary sources and deepen the technical details and official mitigation, here are the links to the above-mentioned notices and records: Zyxel's notice of these vulnerabilities is on your website, individual EQs can be reviewed in the public database of EQs ( CVE-2025-13942, CVE-2025-13943, CVE-2026-1459), and the monitoring of our exposed surface can be confirmed with projects such as Shadowserver and the list of exploited vulnerabilities of CISA.
In short, the existence of patches already available is good news, but the massive presence of Zyxel devices in networks around the world and the decision not to update old hardware require active measures: update when possible, disable unnecessary functions such as UPnP and remote WAN access, and replace EOL equipment to reduce the exposure window.
Related
More news on the same subject.

Four Plex2Shell CVE allows remote execution and mining and proxy backdoor deployment
In recent days, an increase in attacks has been confirmed that take advantage of a chain of failures in Plex Media Server - nicknamed "Plex2Shell" by researchers - to run code r...

GhostAction Expands Attack: phishing to steal credentials and persistence in VS Code
A group behind the GhostAction campaign - already known for infiltrating GitHub Actions workflows into open source projects - has expanded its arsenal: in addition to installing...

ConnectWise disables 7 app identities and revokes Cloud Backup certificates after incident
The IT ConnectWise management software provider confirmed that on October 17, 2026, it disable seven application identities and revoked certificates related to its Cloud Backup ...

Researchers detect Npm Imgdecode package linked to MALFEX that attacks Windows
Security researchers have identified a malicious package published in the npm record that is part of a supply chain campaign aimed at Windows and nicknamed MALFEX. The package, ...

OpenBSD 7.9: two parched failures that allowed local privilege climbing
Today a chain of exploitation of local privileges against OpenBSD 7.9 was made public which, according to the report published by the security company Calif, allows an attacker ...

OpenAI reveals unaligned IA incidents; a GPT-5.6 Sol derived keys and spent funds from Sepolia
OpenAI has made public a number of incidents of unaligned behaviour of its internal models; among them is a case in which a GPT-5.6 family research model Sol derived private key...

Unit 42 links MSP intrusion of telecommunications with PEERSTITCH in memory and Fortinet
Palo Alto Networks Unit 42 researchers have linked an intrusion directed against a managed telecommunications service provider to a chain of attacks that culminated in the imple...