Are your Zyxel broadband routers, ONTs or extenders exposed to CVE-2026-79614?
Zyxel's 17 November 2026 advisory describes an out-of-bounds write in "libclinkc.so" in certain firmware versions of DSL/Ethernet CPE, Fiber ONTs and Wireless Extenders. An unauthenticated attacker could elevate privileges and potentially execute arbitrary commands by sending a crafted HTTP request. Zyxel, as CNA, scores CVE-2026-79614 CVSS 3.1 9.8 Critical in the NVD record. The same advisory covers companion CVE-2026-86676, a post-authentication command injection in the "Description" parameter of a CGI program, scored CVSS 3.1 7.2 High. Zyxel says WAN access is disabled by default on these devices. Apply the patched firmware in Zyxel's tables, or contact your ISP if the unit was ISP-supplied.
Critical (CVSS 9.8). Companion CVE High (CVSS 7.2). Not in CISA KEV
Zyxel's official advisory (initial release 17 November 2026) tells users to install the patches in its tables, and to contact Zyxel sales or support to obtain the file. End-users who acquired the device from an ISP should contact the ISP's support team. The NVD record for CVE-2026-79614, with Zyxel as CNA, scores it CVSS 3.1 9.8 Critical (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, CWE-787). CVE-2026-86676 is CVSS 3.1 7.2 High (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H, CWE-78). Zyxel's advisory, checked at 02:30 GMT on 17 November 2026, does not report exploitation. Neither CVE was in CISA's Known Exploited Vulnerabilities catalogue when we checked at that time (catalogue 2026.11.13, released 20:24 GMT on 13 November 2026). Recheck KEV. We do not treat the absence from KEV as a statement that there has been no exploitation.
By Simon Phillips, CTO. Reviewed by Oliver Legg, Head of SOC and IR. Last updated 18 November 2026, 18:09 GMT.
At a Glance
Based on Zyxel's official advisory (initial release 17 November 2026) and the NVD records for CVE-2026-79614 and CVE-2026-86676, checked at 02:30 GMT on 17 November 2026. CISA KEV catalogue 2026.11.13 was also checked at that time. Last updated 18 November 2026, 18:09 GMT.
Critical, CVSS 3.1 9.8; companion High 7.2
Zyxel as CNA, in the NVD record for CVE-2026-79614: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, base severity Critical, CWE-787. Companion CVE-2026-86676: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H, base severity High, CWE-78. Both NVD records had status Received when we checked at 02:30 GMT on 17 November 2026, and the public NVD HTML detail pages were not yet showing the records. The advisory page itself does not list a score.
No exploitation reported by Zyxel; not in CISA KEV
Zyxel's official advisory, checked at 02:30 GMT on 17 November 2026, does not report exploitation of these vulnerabilities. CVE-2026-79614 and CVE-2026-86676 were not in CISA's Known Exploited Vulnerabilities catalogue when we checked at that time (catalogue 2026.11.13, released 20:24 GMT on 13 November 2026). Recheck KEV. We do not treat the absence from KEV as a statement that there has been no exploitation.
48 models in Table 1; 30 in Table 2
Zyxel's Table 1 lists 48 models for CVE-2026-79614, at the stated version and earlier. Table 2 lists 30 models for CVE-2026-86676 at the specific version shown. One model, PM5311-T0, appears only in Table 2. The NVD records name example products only (DX3301-T0 and EX3301-T0 for CVE-2026-79614; DX3300-T0 for CVE-2026-86676). We show Zyxel's full tables. The tables do not include customized models designed for ISP customers. Zyxel says any product currently on the market that is not listed is not affected.
Patched firmware from Zyxel sales or support, or via your ISP
Follow Zyxel's tables exactly. Contact your Zyxel sales representative or support team to obtain the file. If you acquired the device from an ISP, contact the ISP's support team, as the device may have custom-built settings. ISPs should contact their Zyxel sales or service representatives.
Zyxel publishes the official advisory (revision history: 2026-11-17, initial release) for CVE-2026-79614 and CVE-2026-86676, and lists affected models and patched firmware.
NVD records for both CVEs are published, with Zyxel as CNA. Status was Received when we checked at 02:30 GMT on 17 November 2026.
Neither CVE is in CISA KEV catalogue 2026.11.13 (released 20:24 GMT on 13 November 2026). Zyxel's advisory does not report exploitation.
Inventory the listed models, apply the exact patched firmware or contact your ISP, confirm WAN-side web administration is off, and rotate administrator passwords.
Table 1. Models affected by CVE-2026-79614 (Zyxel advisory)
This table follows Zyxel's official advisory exactly (48 models, counted from the advisory table). Affected versions are written as in the advisory, including "and earlier". Credited to security researchers; we do not name them.
| Product | Affected model | Affected version | Patch availability |
|---|---|---|---|
| DSL/Ethernet CPE | DX3300-T0 | 5.50(ABVY.8.3)C0 and earlier | 5.50(ABVY.8.4)C0 |
| DX3300-T1 | 5.50(ABVY.8.3)C0 and earlier | 5.50(ABVY.8.4)C0 | |
| DX3301-T0 | 5.50(ABVY.8.3)C0 and earlier | 5.50(ABVY.8.4)C0 | |
| DX4510-B0 | 5.17(ABYL.10.4)C0 and earlier | 5.17(ABYL.10.5)C0 | |
| DX4510-B1 | 5.17(ABYL.10.4)C0 and earlier | 5.17(ABYL.10.5)C0 | |
| DX5401-B1 | 5.17(ABYO.7.4)C0 and earlier | 5.17(ABYO.7.5)C0 | |
| EE3301-00 | 5.63(ACMU.3.3)C0 and earlier | 5.63(ACMU.3.4)C0 | |
| EE5301-00 | 5.63(ACLD.3.3)C0 and earlier | 5.63(ACLD.3.4)C0 | |
| EE6510-10 | 5.19(ACJQ.4.4)C0 and earlier | 5.19(ACJQ.4.5)C0 | |
| EMG3525-T50B | 5.50(ABPM.9.11)C0 and earlier | 5.50(ABPM.9.12)C0 | |
| EMG5523-T50B | 5.50(ABPM.9.11)C0 and earlier | 5.50(ABPM.9.12)C0 | |
| EMG6726-B10A | 5.13(ABNP.8.3)C0 and earlier | 5.13(ABNP.8.4)C0 | |
| EX2210-T0 | 5.50(ACDI.2.7)C0 and earlier | 5.50(ACDI.2.8)C0 | |
| EX3300-T0 | 5.50(ABVY.8.3)C0 and earlier | 5.50(ABVY.8.4)C0 | |
| EX3300-T1 | 5.50(ABVY.8.3)C0 and earlier | 5.50(ABVY.8.4)C0 | |
| EX3301-T0 | 5.50(ABVY.8.3)C0 and earlier | 5.50(ABVY.8.4)C0 | |
| EX3500-T0 | 5.44(ACHR.6.1)C0 and earlier | 5.44(ACHR.6.2)C0 | |
| EX3501-T0 | 5.44(ACHR.6.1)C0 and earlier | 5.44(ACHR.6.2)C0 | |
| EX3510-B0 | 5.17(ABUP.15.4)C0 and earlier | 5.17(ABUP.15.5)C0 | |
| EX3510-B1 | 5.17(ABUP.15.4)C0 and earlier | 5.17(ABUP.15.5)C0 | |
| EX3600-T0 | 5.70(ACIF.3.3)C0 and earlier | 5.70(ACIF.3.4)C0 | |
| EX5401-B1 | 5.17(ABYO.7.4)C0 and earlier | 5.17(ABYO.7.5)C0 | |
| EX5510-B0 | 5.17(ABQX.11.3)C0 and earlier | 5.17(ABQX.11.4)C0 | |
| EX5512-T0 | 5.70(ACEG.5.8)C0 and earlier | 5.70(ACEG.5.9)C0 | |
| EX5601-T0 | 5.70(ACDZ.6.3)C0 and earlier | 5.70(ACDZ.6.4)C0 | |
| EX5601-T1 | 5.70(ACDZ.6.3)C0 and earlier | 5.70(ACDZ.6.4)C0 | |
| EX7501-B0 | 5.18(ACHN.3.4)C0 and earlier | 5.18(ACHN.3.5)C0 | |
| EX7710-B0 | 5.18(ACAK.1.9)C0 and earlier | 5.18(ACAK.1.10)C0 | |
| GM4100-B0 | 5.18(ACCL.2.2)C0 and earlier | 5.18(ACCL.3)C0 | |
| VMG3625-T50B | 5.50(ABPM.9.11)C0 and earlier | 5.50(ABPM.9.12)C0 | |
| VMG3927-T50K | 5.13(ABLY.10.3)C0 and earlier | 5.13(ABLY.10.4)C0 | |
| VMG4005-B50A | 5.17(ABQA.3.5)C0 and earlier | 5.17(ABQA.3.6)C0 | |
| VMG4005-B50B | 5.13(ABRL.5.6)C0 and earlier | 5.13(ABRL.5.7)C0 | |
| VMG4005-B60A | 5.17(ABQA.3.5)C0 and earlier | 5.17(ABQA.3.6)C0 | |
| VMG4927-B50A | 5.13(ABLY.10.3)C0 and earlier | 5.13(ABLY.10.4)C0 | |
| VMG8623-T50B | 5.50(ABPM.9.11)C0 and earlier | 5.50(ABPM.9.12)C0 | |
| Fiber ONTs | AM7510-00 | 5.63(ACOR.0.4)C0 and earlier | 5.63(ACOR.0.5)C0 |
| AX7501-B1 | 5.17(ABPC.8.1)C0 and earlier | 5.17(ABPC.8.2)C0 | |
| PE5301-01 | 5.63(ACOJ.3.3)C0 and earlier | 5.63(ACOJ.3.4)C0 | |
| PM3100-T0 | 5.42(ACBF.4.5)C0 and earlier | 5.42(ACBF.4.6)C0 | |
| PM5100-T0 | 5.42(ACBF.4.5)C0 and earlier | 5.42(ACBF.4.6)C0 | |
| PM5100-T1 | 5.42(ACBF.4.5)C0 and earlier | 5.42(ACBF.4.6)C0 | |
| PM7300-T0 | 5.42(ABYY.4.3)C0 and earlier | 5.42(ABYY.4.4)C0 | |
| PM7500-00 | 5.61(ACKK.1.6)C0 and earlier | 5.61(ACKK.1.7)C0 | |
| Wireless Extenders | WE3300-00 | 5.70(ACKA.2.1)C0 and earlier | 5.70(ACKA.2.2)C0 |
| WX3100-T0 | 5.50(ABVL.5.2)C0 and earlier | 5.50(ABVL.5.3)C0 | |
| WX5600-T0 | 5.70(ACEB.6.4)C0 and earlier | 5.70(ACEB.6.5)C0 | |
| WX5610-B0 | 5.18(ACGJ.0.6)C0 and earlier | 5.18(ACGJ.0.7)C0 |
Zyxel marks patch availability with an asterisk: please contact your Zyxel sales representative or support team to obtain the file.
Table 2. Models affected by CVE-2026-86676 (Zyxel advisory)
This table follows Zyxel's official advisory exactly (30 models, counted from the advisory table). The advisory lists a specific affected version in this table and does not add "and earlier". PM5311-T0 appears only in this table. Credited to security researchers; we do not name them.
| Product | Affected model | Affected version | Patch availability |
|---|---|---|---|
| DSL/Ethernet CPE | DX3300-T0 | 5.50(ABVY.8.3)C0 | 5.50(ABVY.8.4)C0 |
| DX3300-T1 | 5.50(ABVY.8.3)C0 | 5.50(ABVY.8.4)C0 | |
| DX3301-T0 | 5.50(ABVY.8.3)C0 | 5.50(ABVY.8.4)C0 | |
| DX4510-B0 | 5.17(ABYL.10.4)C0 | 5.17(ABYL.10.5)C0 | |
| DX4510-B1 | 5.17(ABYL.10.4)C0 | 5.17(ABYL.10.5)C0 | |
| DX5401-B1 | 5.17(ABYO.7.4)C0 | 5.17(ABYO.7.5)C0 | |
| EE3301-00 | 5.63(ACMU.3.3)C0 | 5.63(ACMU.3.4)C0 | |
| EE5301-00 | 5.63(ACLD.3.3)C0 | 5.63(ACLD.3.4)C0 | |
| EE6510-10 | 5.19(ACJQ.4.4) C0 | 5.19(ACJQ.4.5) C0 | |
| EMG3525-T50B | 5.50(ABPM.9.11)C0 | 5.50(ABPM.9.12)C0 | |
| EMG5523-T50B | 5.50(ABPM.9.11)C0 | 5.50(ABPM.9.12)C0 | |
| EX2210-T0 | 5.50(ACDI.2.7)C0 | 5.50(ACDI.2.8)C0 | |
| EX3300-T0 | 5.50(ABVY.8.3)C0 | 5.50(ABVY.8.4)C0 | |
| EX3300-T1 | 5.50(ABVY.8.3)C0 | 5.50(ABVY.8.4)C0 | |
| EX3301-T0 | 5.50(ABVY.8.3)C0 | 5.50(ABVY.8.4)C0 | |
| EX3500-T0 | 5.44(ACHR.6.1)C0 | 5.44(ACHR.6.2)C0 | |
| EX3501-T0 | 5.44(ACHR.6.1)C0 | 5.44(ACHR.6.2)C0 | |
| EX3600-T0 | 5.70(ACIF.3.3)C0 | 5.70(ACIF.3.4)C0 | |
| EX5401-B1 | 5.17(ABYO.7.4)C0 | 5.17(ABYO.7.5)C0 | |
| EX5510-B0 | 5.17(ABQX.11.3)C0 | 5.17(ABQX.11.4)C0 | |
| EX5601-T0 | 5.70(ACDZ.6.3)C0 | 5.70(ACDZ.6.4)C0 | |
| EX5601-T1 | 5.70(ACDZ.6.3)C0 | 5.70(ACDZ.6.4)C0 | |
| EX7501-B0 | 5.18(ACHN.3.4)C0 | 5.18(ACHN.3.5)C0 | |
| EX7710-B0 | 5.18(ACAK.1.9)C0 | 5.18(ACAK.1.10)C0 | |
| VMG3625-T50B | 5.50(ABPM.9.11)C0 | 5.50(ABPM.9.12)C0 | |
| VMG8623-T50B | 5.50(ABPM.9.11)C0 | 5.50(ABPM.9.12)C0 | |
| Fiber ONTs | AX7501-B1 | 5.17(ABPC.8.1)C0 | 5.17(ABPC.8.2)C0 |
| PE5301-01 | 5.63(ACOJ.3.3)C0 | 5.63(ACOJ.3.4)C0 | |
| PM5311-T0 | 1.00(ACFG.3)C0 | 1.00(ACFG.3.2)C0 | |
| Wireless Extenders | WX5610-B0 | 5.18(ACGJ.0.6)C0 | 5.18(ACGJ.0.7)C0 |
Zyxel marks patch availability with an asterisk: please contact your Zyxel sales representative or support team to obtain the file.
What to Do in the Next 24 Hours
Proactive on the left. Reactive on the right. Vendor steps and our advice are labelled separately.
Apply the patched firmware
- Zyxel: install the patches listed in the official advisory tables. Contact your Zyxel sales representative or support team to obtain the file.
- Zyxel: if you acquired the device from an ISP, contact the ISP's support team, as the device may have custom-built settings.
- Our advice: inventory Zyxel DSL/Ethernet CPE, fibre ONTs and wireless extenders across client sites, including SOHO and home-worker units. Compare each model and firmware string with both of Zyxel's tables.
- Our advice: confirm WAN-side web administration and remote management are off. Zyxel says WAN access is disabled by default. Check whether any unit has had its web administration interface exposed to the internet.
- Our advice: rotate administrator passwords, and keep the administration interface off guest and IoT LANs.
Hunt and contain
- Our advice: Zyxel's advisory does not publish indicators of compromise. Look for unexpected configuration changes, new administrator accounts, and changes to DNS or port forwarding.
- Our advice: look for unexpected outbound connections from the device, and for unexpected reboots or crashes.
- Our advice: look for unexpected access to the web administration interface, including from unusual addresses.
- Our advice: if you find signs of misuse, isolate the device, keep its logs and a saved configuration, factory reset the device, flash the patched firmware from Zyxel's table, reconfigure from a known-good baseline, and rotate credentials.
Proactive: Vendor Steps, Then Ours
Zyxel's official advisory first. CybaVerse advice is labelled separately.
Install the patched firmware for each listed model
Follow Zyxel's official advisory tables exactly. Each listed model has its own patched build. Contact your Zyxel sales representative or support team to obtain the file. For CVE-2026-79614, treat the stated version and earlier as affected. For CVE-2026-86676, the advisory lists a specific affected version. As an example, DX3301-T0 and EX3301-T0 firmware 5.50(ABVY.8.3)C0 and earlier are affected by CVE-2026-79614, and the patched build is 5.50(ABVY.8.4)C0.
ISP-supplied and ISP-customised units
Zyxel says the tables do not include customized models specifically designed for ISP customers. End-users who acquired their Zyxel device from an ISP should contact the ISP's support team, as the device may have custom-built settings. ISPs should contact their Zyxel sales or service representatives for further details.
Inventory model and firmware
Record every listed Zyxel broadband router, ONT and extender you or your clients run, including SOHO and home-worker units. Compare each model and firmware string with both tables. On-market products not listed are, in Zyxel's words, not affected.
Confirm WAN access is off, and restrict the web UI
Zyxel says WAN access is disabled by default on these devices. Confirm that WAN-side web administration and remote management are still off, and check whether any unit has had its web administration interface exposed to the internet. Restrict which hosts can reach the web UI from the LAN. For CVE-2026-86676, Zyxel says the attack can succeed only if user-configured passwords have been compromised; rotate administrator passwords and keep admin access off guest and IoT LANs.
Free Detection Pack
Built by the CybaVerse threat hunt team for businesses, internal IT teams and MSPs. Check exposure offline and hunt for signs of misuse. Everything is read-only. The KQL in this pack has not been run against a live tenant.
check-zyxel-cpe-ont.sh
Read-only offline checker. It compares a model and firmware string, or an inventory CSV, with Zyxel's two advisory tables. Unpack the full pack first, so scripts/ and data/zyxel-2026-11-17-models.csv stay together. Table 1 (CVE-2026-79614, 48 models) uses the stated version and earlier. Table 2 (CVE-2026-86676, 30 models) matches the exact listed build. An ISP-supplied unit (--isp, or supplied_by=isp) is always UNKNOWN, because Zyxel's tables exclude ISP-customised models. On-market products not listed are, in Zyxel's words, not affected.
bash scripts/check-zyxel-cpe-ont.sh --model DX3301-T0 --firmware '5.50(ABVY.8.3)C0'
bash scripts/check-zyxel-cpe-ont.sh --inventory devices.csvCheck-ZyxelCpeOnt.ps1
The same checks in PowerShell 7, with identical output and exit codes. Run it from the unpacked full pack so the script can read the model data file.
pwsh -File scripts/Check-ZyxelCpeOnt.ps1 --model DX3301-T0 --firmware '5.50(ABVY.8.3)C0'
pwsh -File scripts/Check-ZyxelCpeOnt.ps1 --inventory devices.csvKQL and Sigma
9 KQL hunts for Microsoft Sentinel and Defender: Q1a and Q1b inventory (Zyxel's model list and the two CVE IDs); Q2a and Q2b admin UI exposure; Q3 oversized HTTP; Q4 a Description parameter with shell metacharacters; Q5 new outbound connections from a device. Q4b and Q6 use Syslog and are unverified (Zyxel publishes no log format). Ports 80 and 443 in Q2a, Q2b and the Sigma rules are our assumption; Zyxel publishes no port. 5 Sigma rules cover admin-port inbound, device outbound, web UI access, oversized URIs and Description shell characters, with Kusto conversions included. The KQL has not been run against a live tenant. Zyxel has published no indicators of compromise. These hunts, except the two inventory queries, are our pattern, not vendor guidance.
Verdicts
- FIXEDThe firmware is at or past the patched build in Zyxel's table for that model and CVE.
- AFFECTEDTable 1: the stated version or earlier for CVE-2026-79614. Table 2: the exact listed build for CVE-2026-86676.
- UNKNOWNISP-supplied unit, unreadable model or firmware, a different firmware line, or a build not in Zyxel's table (including Table 2 builds earlier than the listed version).
- NOT LISTEDThe model is not in either of Zyxel's tables. Zyxel says on-market products not listed are not affected; review these rows.
Exit codes
| Code | Meaning |
|---|---|
| 0 | Every device FIXED |
| 1 | Any AFFECTED |
| 3 | Any UNKNOWN (including an ISP-supplied unit), and none AFFECTED |
| 5 | Only FIXED and NOT LISTED devices (review) |
| 4 | Usage, input or data file error |
The full pack zip contains 30 files, counted from the threat-hunt store. README and Sigma files are inside that zip as well as available separately.
What is in the pack
| File | What it does |
|---|---|
| scripts/check-zyxel-cpe-ont.sh | Offline checker for Linux and macOS (bash) |
| scripts/Check-ZyxelCpeOnt.ps1 | The same checker in PowerShell 7 |
| data/zyxel-2026-11-17-models.csv | Zyxel's Table 1 and Table 2, transcribed verbatim |
| KQL (9 hunts) | Q1a and Q1b inventory; Q2a and Q2b admin UI exposure; Q3 oversized HTTP; Q4 Description shell characters; Q5 new outbound; Q4b and Q6 Syslog (unverified) |
| Sigma (5 rules) | Admin-port inbound, device outbound, web UI access, oversized URI and Description shell-character rules, plus Kusto conversions |
| tests/ | Fixtures and tests |
| README.md | Verified facts, vendor advice vs our advice, limits and usage |
Reactive: How to Hunt (Our Advice)
Zyxel's advisory does not publish indicators of compromise. The hunts below are CybaVerse advice. CybaOps can run them across your estate.
Administrator accounts and configuration changes
Review device logs and the current configuration for unexpected administrator logins, new administrator accounts, and unexpected changes, including DNS and port forwarding. Pack hunt Q6 looks for related Syslog events, but it is unverified because Zyxel publishes no log format.
Reboots and outbound traffic
Look for unexpected reboots or crashes, and for unexpected outbound connections from the device (pack hunt Q5 is our pattern for new outbound connections from a device address).
Access to the web administration interface
Look for unexpected access to the web administration interface, including from unusual internal addresses, and confirm whether the interface is reachable from the internet (pack hunts Q2a and Q2b). Ports 80 and 443 in those hunts are our assumption; Zyxel publishes no port.
If you find signs of compromise (our advice)
- Isolate the device from untrusted networks and keep its logs and a saved configuration.
- Factory reset the device, then flash the exact patched firmware for that model from Zyxel's table (or the ISP-supplied image, if the unit came from an ISP).
- Reconfigure from a known-good baseline, and rotate administrator credentials, plus any other credentials stored on or reused by the device.
- Review traffic from the device for unexpected destinations, and start incident response if the device sits in a path that can reach wider management or production networks.
Zyxel CPE CVE-2026-79614 FAQ
Short answers based on Zyxel's official advisory and the NVD records, rechecked at 02:30 GMT on 17 November 2026.
What is CVE-2026-79614, and what is CVE-2026-86676?
Zyxel's official advisory, initial release 17 November 2026, describes CVE-2026-79614 as an out-of-bounds write vulnerability in "libclinkc.so" in certain firmware versions of DSL/Ethernet CPE, Fiber ONTs and Wireless Extenders. Zyxel says an unauthenticated attacker could elevate privileges and potentially execute arbitrary commands by sending a crafted HTTP request. The same advisory describes CVE-2026-86676 as a post-authentication command injection vulnerability in the "Description" parameter of a CGI program. Zyxel says an authenticated attacker with administrator privileges could execute OS commands by sending a crafted HTTP request, and that this attack can succeed only if user-configured passwords have been compromised. For both CVEs, Zyxel says WAN access is disabled by default on these devices. Credited to security researchers; we do not name them.
How severe are they?
The NVD record for CVE-2026-79614, with Zyxel as CNA, lists CVSS 3.1 9.8 Critical, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, and CWE-787. The NVD record for CVE-2026-86676, with Zyxel as CNA, lists CVSS 3.1 7.2 High, vector CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H, and CWE-78. Both records had status Received when we checked at 02:30 GMT on 17 November 2026, and the public NVD HTML detail pages were not yet showing the records at that check. The advisory page itself does not list a CVSS score. We use the NVD records (Zyxel as CNA) for the scores, and we label each CVE as those records do.
Is either CVE in CISA KEV, and has exploitation been reported?
Zyxel's official advisory, checked at 02:30 GMT on 17 November 2026, does not report exploitation of these vulnerabilities. CVE-2026-79614 and CVE-2026-86676 were not in CISA's Known Exploited Vulnerabilities catalogue when we checked at that time. That catalogue (2026.11.13) was released at 20:24 GMT on 13 November 2026. Recheck KEV. We do not treat the absence from KEV as a statement that there has been no exploitation.
Which models and versions are affected?
Follow Zyxel's tables exactly. Table 1 lists 48 models affected by CVE-2026-79614, each at the stated firmware version and earlier, with a patched build in the same row. Table 2 lists 30 models affected by CVE-2026-86676 at the specific firmware version shown (the advisory does not add "and earlier" in Table 2). One model, PM5311-T0, appears only in Table 2, at 1.00(ACFG.3)C0, patched in 1.00(ACFG.3.2)C0. As an example from Table 1 and the NVD record, DX3301-T0 and EX3301-T0 firmware 5.50(ABVY.8.3)C0 and earlier are affected by CVE-2026-79614, and the patched build is 5.50(ABVY.8.4)C0. Zyxel says the tables do not include customized models specifically designed for ISP customers, and that any product currently on the market that is not listed in the tables is not affected.
What is Zyxel's official advice?
Zyxel has released firmware patches for the affected products that were still within their vulnerability support period, and tells users to install those patches to ensure optimal protection. The advisory says to contact your Zyxel sales representative or support team to obtain the file. For ISPs, Zyxel says to contact your Zyxel sales or service representatives for further details. For end-users who acquired their Zyxel device from an ISP, Zyxel recommends reaching out directly to the ISP's support team, as the device may have custom-built settings.
Who is this relevant to?
Organisations and MSPs that run the listed Zyxel DSL/Ethernet CPE, fibre ONTs or wireless extenders, including SOHO and home-worker units, and especially any device whose web administration interface is reachable from the internet or from a LAN that is not fully trusted. If the unit was supplied by an ISP, the ISP's support team is the route Zyxel gives for a patch.
Need help checking every Zyxel router, ONT and extender you manage?
CybaOps monitors your servers, endpoints and cloud workloads, whether that's your own business or your clients'. UK-based analysts monitor alerts 24/7, run these threat hunts and act on pre-approved response actions. The CybaOps Remediation Engine is live: it can fix security issues automatically, so gaps get closed rather than just reported. CybaRemediate, our remediation product line built on the Remediation Engine, is live. Book a CybaOps demo and see the Remediation Engine close a gap.
Sources
- Zyxel security advisory for out-of-bounds write and post-authentication command injection vulnerabilities in certain DSL/Ethernet CPE, Fiber ONTs, and Wireless Extenders (initial release 17 November 2026)
- NVD: CVE-2026-79614 (CNA: Zyxel; CVSS 3.1 9.8 Critical, CWE-787; status Received when checked at 02:30 GMT on 17 November 2026)
- NVD: CVE-2026-86676 (CNA: Zyxel; CVSS 3.1 7.2 High, CWE-78; status Received when checked at 02:30 GMT on 17 November 2026)
Related threat guide: Zyxel GS1900 CVE-2026-107441. All threat guides.