# Zyxel DSL/Ethernet CPE, fibre ONTs and wireless extenders: CVE-2026-79614 and CVE-2026-86676 (pack v1.0.0)

Detection and checking pack for the Zyxel security advisory of 17 Nov 2026 (Initial release). Built 17 Nov 2026 by CybaVerse.
Sources cited: Zyxel, NVD, cve.org, CISA KEV and MITRE ATT&CK only. Everything labelled OUR is CybaVerse's own heuristic or
advice, not Zyxel's.

**Caveat: the KQL in this pack has NOT been run against a live tenant.** It was parsed offline with Kusto.Language against an
assumed schema subset. The Sigma rules are untested against live data. Zyxel publishes no IOCs, URI paths, ports, headers or log
formats for these CVEs, so every hunt except the two inventory queries is OUR PATTERN.

## What it is

| Item | CVE-2026-79614 | CVE-2026-86676 |
|---|---|---|
| Flaw (Zyxel) | Out-of-bounds write in "libclinkc.so" | Post-authentication command injection in the "Description" parameter of a CGI program |
| Who can trigger it (Zyxel) | An unauthenticated attacker, by sending a crafted HTTP request | An authenticated attacker with administrator privileges, by sending a crafted HTTP request |
| Impact (Zyxel) | Could elevate privileges and potentially execute arbitrary commands | Could execute OS commands |
| Condition (Zyxel) | WAN access is disabled by default on these devices | WAN access is disabled by default; the attack can succeed only if user-configured passwords have been compromised |
| CNA score | Zyxel as CNA: 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 | Zyxel as CNA: 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 |
| NVD | Published 17 Nov 2026 02:17 GMT, status Received; shows the Zyxel score (Primary) and has no NVD score of its own | Same: published 17 Nov 2026 02:17 GMT, status Received, Zyxel score only |
| Weakness | CWE-787 Out-of-bounds write | CWE-78 OS command injection |
| cve.org record | Published 17 Nov 2026 01:43 GMT; affected products listed: DX3301-T0 and EX3301-T0 firmware through 5.50(ABVY.8.3)C0 | Published 17 Nov 2026 01:51 GMT; affected product listed: DX3300-T0 firmware through 5.50(ABVY.8.3)C0 |
| CISA KEV | Not listed (catalog 2026.11.13, checked 17 Nov 2026 02:30 GMT) | Not listed (same check) |
| Exploitation | Zyxel's advisory does not mention exploitation | Zyxel's advisory does not mention exploitation |

Zyxel on CVE-2026-86676: "WAN access is disabled by default on these devices, and this attack can succeed only if
user-configured passwords have been compromised."

Only CVE-2026-79614 is called Critical, because that is the CNA's 9.8 rating. CVE-2026-86676 keeps the CNA's High rating
(7.2) everywhere in this pack.

The cve.org and NVD records name only one or two example models; Zyxel's advisory tables (below) are the full list and are what
the checker uses.

KEV: neither CVE is in the CISA Known Exploited Vulnerabilities catalog at the time of writing. If either is added, KEV due dates
apply to US federal agencies under BOD 26-04 only. Patch now regardless.

ATT&CK mapping (OUR): T1190 Exploit Public-Facing Application, T1068 Exploitation for Privilege Escalation, T1059.004 Command and
Scripting Interpreter: Unix Shell, T1071.001 Application Layer Protocol: Web Protocols, T1584.008 Compromise Infrastructure:
Network Devices, T1565.002 Data Manipulation: Transmitted Data Manipulation (for DNS changes).

Credit: Zyxel thanks two security researchers, one for each CVE.

## Affected models (transcribed exactly from Zyxel's two tables)

Zyxel: "Please note that the tables do not include customized models specifically designed for ISP customers. Any product
currently on the market that is not listed in the tables is not affected." Zyxel lists products "still within their
vulnerability support period".

Counts verified from the advisory HTML: Table 1 has 48 models, Table 2 has 30 models, 49 distinct models across both. PM5311-T0
is the only model in Table 2 that is not in Table 1. The two tables are kept as two separate maps in
`data/zyxel-2026-11-17-models.csv` and in the checker.

Version semantics as printed by Zyxel: every Table 1 cell reads "and earlier". Table 2 cells name one build each, without "and
earlier", so the checker treats Table 2 as an exact build match: the listed build is AFFECTED, the patch or later is FIXED, and
any other build of a Table 2 model is UNKNOWN for CVE-2026-86676 (Zyxel's table does not say). A Table 1 model that is also in
Table 2 is still AFFECTED by CVE-2026-79614 for earlier builds.

### Table 1. Models affected by CVE-2026-79614 (48)

| 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 |
| DSL/Ethernet CPE | DX3300-T1 | 5.50(ABVY.8.3)C0 and earlier | 5.50(ABVY.8.4)C0 |
| DSL/Ethernet CPE | DX3301-T0 | 5.50(ABVY.8.3)C0 and earlier | 5.50(ABVY.8.4)C0 |
| DSL/Ethernet CPE | DX4510-B0 | 5.17(ABYL.10.4)C0 and earlier | 5.17(ABYL.10.5)C0 |
| DSL/Ethernet CPE | DX4510-B1 | 5.17(ABYL.10.4)C0 and earlier | 5.17(ABYL.10.5)C0 |
| DSL/Ethernet CPE | DX5401-B1 | 5.17(ABYO.7.4)C0 and earlier | 5.17(ABYO.7.5)C0 |
| DSL/Ethernet CPE | EE3301-00 | 5.63(ACMU.3.3)C0 and earlier | 5.63(ACMU.3.4)C0 |
| DSL/Ethernet CPE | EE5301-00 | 5.63(ACLD.3.3)C0 and earlier | 5.63(ACLD.3.4)C0 |
| DSL/Ethernet CPE | EE6510-10 | 5.19(ACJQ.4.4)C0 and earlier | 5.19(ACJQ.4.5)C0 |
| DSL/Ethernet CPE | EMG3525-T50B | 5.50(ABPM.9.11)C0 and earlier | 5.50(ABPM.9.12)C0 |
| DSL/Ethernet CPE | EMG5523-T50B | 5.50(ABPM.9.11)C0 and earlier | 5.50(ABPM.9.12)C0 |
| DSL/Ethernet CPE | EMG6726-B10A | 5.13(ABNP.8.3)C0 and earlier | 5.13(ABNP.8.4)C0 |
| DSL/Ethernet CPE | EX2210-T0 | 5.50(ACDI.2.7)C0 and earlier | 5.50(ACDI.2.8)C0 |
| DSL/Ethernet CPE | EX3300-T0 | 5.50(ABVY.8.3)C0 and earlier | 5.50(ABVY.8.4)C0 |
| DSL/Ethernet CPE | EX3300-T1 | 5.50(ABVY.8.3)C0 and earlier | 5.50(ABVY.8.4)C0 |
| DSL/Ethernet CPE | EX3301-T0 | 5.50(ABVY.8.3)C0 and earlier | 5.50(ABVY.8.4)C0 |
| DSL/Ethernet CPE | EX3500-T0 | 5.44(ACHR.6.1)C0 and earlier | 5.44(ACHR.6.2)C0 |
| DSL/Ethernet CPE | EX3501-T0 | 5.44(ACHR.6.1)C0 and earlier | 5.44(ACHR.6.2)C0 |
| DSL/Ethernet CPE | EX3510-B0 | 5.17(ABUP.15.4)C0 and earlier | 5.17(ABUP.15.5)C0 |
| DSL/Ethernet CPE | EX3510-B1 | 5.17(ABUP.15.4)C0 and earlier | 5.17(ABUP.15.5)C0 |
| DSL/Ethernet CPE | EX3600-T0 | 5.70(ACIF.3.3)C0 and earlier | 5.70(ACIF.3.4)C0 |
| DSL/Ethernet CPE | EX5401-B1 | 5.17(ABYO.7.4)C0 and earlier | 5.17(ABYO.7.5)C0 |
| DSL/Ethernet CPE | EX5510-B0 | 5.17(ABQX.11.3)C0 and earlier | 5.17(ABQX.11.4)C0 |
| DSL/Ethernet CPE | EX5512-T0 | 5.70(ACEG.5.8)C0 and earlier | 5.70(ACEG.5.9)C0 |
| DSL/Ethernet CPE | EX5601-T0 | 5.70(ACDZ.6.3)C0 and earlier | 5.70(ACDZ.6.4)C0 |
| DSL/Ethernet CPE | EX5601-T1 | 5.70(ACDZ.6.3)C0 and earlier | 5.70(ACDZ.6.4)C0 |
| DSL/Ethernet CPE | EX7501-B0 | 5.18(ACHN.3.4)C0 and earlier | 5.18(ACHN.3.5)C0 |
| DSL/Ethernet CPE | EX7710-B0 | 5.18(ACAK.1.9)C0 and earlier | 5.18(ACAK.1.10)C0 |
| DSL/Ethernet CPE | GM4100-B0 | 5.18(ACCL.2.2)C0 and earlier | 5.18(ACCL.3)C0 |
| DSL/Ethernet CPE | VMG3625-T50B | 5.50(ABPM.9.11)C0 and earlier | 5.50(ABPM.9.12)C0 |
| DSL/Ethernet CPE | VMG3927-T50K | 5.13(ABLY.10.3)C0 and earlier | 5.13(ABLY.10.4)C0 |
| DSL/Ethernet CPE | VMG4005-B50A | 5.17(ABQA.3.5)C0 and earlier | 5.17(ABQA.3.6)C0 |
| DSL/Ethernet CPE | VMG4005-B50B | 5.13(ABRL.5.6)C0 and earlier | 5.13(ABRL.5.7)C0 |
| DSL/Ethernet CPE | VMG4005-B60A | 5.17(ABQA.3.5)C0 and earlier | 5.17(ABQA.3.6)C0 |
| DSL/Ethernet CPE | VMG4927-B50A | 5.13(ABLY.10.3)C0 and earlier | 5.13(ABLY.10.4)C0 |
| DSL/Ethernet CPE | 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 |
| Fiber ONTs | AX7501-B1 | 5.17(ABPC.8.1)C0 and earlier | 5.17(ABPC.8.2)C0 |
| Fiber ONTs | PE5301-01 | 5.63(ACOJ.3.3)C0 and earlier | 5.63(ACOJ.3.4)C0 |
| Fiber ONTs | PM3100-T0 | 5.42(ACBF.4.5)C0 and earlier | 5.42(ACBF.4.6)C0 |
| Fiber ONTs | PM5100-T0 | 5.42(ACBF.4.5)C0 and earlier | 5.42(ACBF.4.6)C0 |
| Fiber ONTs | PM5100-T1 | 5.42(ACBF.4.5)C0 and earlier | 5.42(ACBF.4.6)C0 |
| Fiber ONTs | PM7300-T0 | 5.42(ABYY.4.3)C0 and earlier | 5.42(ABYY.4.4)C0 |
| Fiber ONTs | 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 |
| Wireless Extenders | WX3100-T0 | 5.50(ABVL.5.2)C0 and earlier | 5.50(ABVL.5.3)C0 |
| Wireless Extenders | WX5600-T0 | 5.70(ACEB.6.4)C0 and earlier | 5.70(ACEB.6.5)C0 |
| Wireless Extenders | WX5610-B0 | 5.18(ACGJ.0.6)C0 and earlier | 5.18(ACGJ.0.7)C0 |

### Table 2. Models affected by CVE-2026-86676 (30)

| Product | Affected model | Affected version | Patch availability |
|---|---|---|---|
| DSL/Ethernet CPE | DX3300-T0 | 5.50(ABVY.8.3)C0 | 5.50(ABVY.8.4)C0 |
| DSL/Ethernet CPE | DX3300-T1 | 5.50(ABVY.8.3)C0 | 5.50(ABVY.8.4)C0 |
| DSL/Ethernet CPE | DX3301-T0 | 5.50(ABVY.8.3)C0 | 5.50(ABVY.8.4)C0 |
| DSL/Ethernet CPE | DX4510-B0 | 5.17(ABYL.10.4)C0 | 5.17(ABYL.10.5)C0 |
| DSL/Ethernet CPE | DX4510-B1 | 5.17(ABYL.10.4)C0 | 5.17(ABYL.10.5)C0 |
| DSL/Ethernet CPE | DX5401-B1 | 5.17(ABYO.7.4)C0 | 5.17(ABYO.7.5)C0 |
| DSL/Ethernet CPE | EE3301-00 | 5.63(ACMU.3.3)C0 | 5.63(ACMU.3.4)C0 |
| DSL/Ethernet CPE | EE5301-00 | 5.63(ACLD.3.3)C0 | 5.63(ACLD.3.4)C0 |
| DSL/Ethernet CPE | EE6510-10 | 5.19(ACJQ.4.4) C0 | 5.19(ACJQ.4.5) C0 |
| DSL/Ethernet CPE | EMG3525-T50B | 5.50(ABPM.9.11)C0 | 5.50(ABPM.9.12)C0 |
| DSL/Ethernet CPE | EMG5523-T50B | 5.50(ABPM.9.11)C0 | 5.50(ABPM.9.12)C0 |
| DSL/Ethernet CPE | EX2210-T0 | 5.50(ACDI.2.7)C0 | 5.50(ACDI.2.8)C0 |
| DSL/Ethernet CPE | EX3300-T0 | 5.50(ABVY.8.3)C0 | 5.50(ABVY.8.4)C0 |
| DSL/Ethernet CPE | EX3300-T1 | 5.50(ABVY.8.3)C0 | 5.50(ABVY.8.4)C0 |
| DSL/Ethernet CPE | EX3301-T0 | 5.50(ABVY.8.3)C0 | 5.50(ABVY.8.4)C0 |
| DSL/Ethernet CPE | EX3500-T0 | 5.44(ACHR.6.1)C0 | 5.44(ACHR.6.2)C0 |
| DSL/Ethernet CPE | EX3501-T0 | 5.44(ACHR.6.1)C0 | 5.44(ACHR.6.2)C0 |
| DSL/Ethernet CPE | EX3600-T0 | 5.70(ACIF.3.3)C0 | 5.70(ACIF.3.4)C0 |
| DSL/Ethernet CPE | EX5401-B1 | 5.17(ABYO.7.4)C0 | 5.17(ABYO.7.5)C0 |
| DSL/Ethernet CPE | EX5510-B0 | 5.17(ABQX.11.3)C0 | 5.17(ABQX.11.4)C0 |
| DSL/Ethernet CPE | EX5601-T0 | 5.70(ACDZ.6.3)C0 | 5.70(ACDZ.6.4)C0 |
| DSL/Ethernet CPE | EX5601-T1 | 5.70(ACDZ.6.3)C0 | 5.70(ACDZ.6.4)C0 |
| DSL/Ethernet CPE | EX7501-B0 | 5.18(ACHN.3.4)C0 | 5.18(ACHN.3.5)C0 |
| DSL/Ethernet CPE | EX7710-B0 | 5.18(ACAK.1.9)C0 | 5.18(ACAK.1.10)C0 |
| DSL/Ethernet CPE | VMG3625-T50B | 5.50(ABPM.9.11)C0 | 5.50(ABPM.9.12)C0 |
| DSL/Ethernet CPE | 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 |
| Fiber ONTs | PE5301-01 | 5.63(ACOJ.3.3)C0 | 5.63(ACOJ.3.4)C0 |
| Fiber ONTs | 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: "* Please contact your Zyxel sales representative or support team to obtain the file."

Rows read exactly but printed in an unusual form (kept as printed; no row was unreadable):
- CVE-2026-79614 GM4100-B0: READ EXACTLY: patch build printed as ACCL.3 (two parts) while the affected build is ACCL.2.2; kept as printed
- CVE-2026-86676 EE6510-10: READ EXACTLY: Zyxel prints a space before C0 in both cells; kept as printed; the checker ignores spaces
- CVE-2026-86676 PM5311-T0: READ EXACTLY: model appears only in Table 2 (CVE-2026-86676)

## Fix (Zyxel)

- Install the patch build in the "Patch availability" column. Zyxel: "Please contact your Zyxel sales representative or support
  team to obtain the file."
- Zyxel: "For ISPs, please contact your Zyxel sales or service representatives for further details."
- Zyxel: "For end-users who acquired their Zyxel device from an ISP, we recommend reaching out directly to the ISP's support
  team, as the device may have custom-built settings."

## Zyxel advice (credited to Zyxel)

1. **Install the patches.** Zyxel: users "are strongly advised to install these patches to ensure optimal protection."
2. **Get the file from Zyxel sales or support**, or, for ISP-supplied devices, from the ISP's support team.
3. **WAN access is disabled by default** on these devices (Zyxel), which narrows exposure to the LAN unless it was changed.

## OUR ADVICE (CybaVerse)

Not Zyxel guidance. Proactive:

1. **Inventory SOHO and home-worker devices.** List every Zyxel router, ONT and extender at client sites and home workers, with
   model, firmware and who supplied it (retail or ISP). Run `scripts/check-zyxel-cpe-ont.sh --inventory` over the list.
2. **Turn off WAN-side management.** Confirm web and remote management are not reachable from the WAN, and remove any port
   forwarding to the admin interface.
3. **Check external exposure** of device admin interfaces with your attack-surface tooling and with hunt Q2a.
4. **Patch, or chase the ISP.** Install the patch build; for ISP-supplied units, ask the ISP for the fixed firmware and a date.
5. **Rotate admin passwords** on every listed device (CVE-2026-86676 needs administrator credentials).
6. **Separate admin access from guest and IoT LANs** so only trusted hosts can reach the web UI.

Reactive, if a device may be compromised:

7. **Factory reset** the device.
8. **Flash the patched firmware** before reconnecting it.
9. **Rebuild the configuration from a known-good baseline**, not from a backup taken after the suspected compromise.
10. **Rotate credentials**: device admin, Wi-Fi, PPPoE or ISP credentials, and any VPN or cloud accounts configured on it.
11. **Review traffic** for unexpected DNS servers, new port forwards, new admin accounts, unusual outbound connections from the
    device and signs it was used to pivot into the LAN (hunts Q5 and Q6).

## Pack contents

| Path | What it is |
|---|---|
| `data/zyxel-2026-11-17-models.csv` | Zyxel's Table 1 and Table 2, transcribed verbatim (78 rows, 49 models), with a flag column |
| `kql/zyxel-cpe-ont-cve-2026-79614-86676-hunting.kql` | 9 queries (2 INVENTORY, 7 OUR PATTERN) |
| `sigma/*.yml` | 5 rules, all OUR PATTERN; Kusto conversions in `sigma/converted/` |
| `scripts/check-zyxel-cpe-ont.sh`, `scripts/Check-ZyxelCpeOnt.ps1` | Offline checkers with identical output and exit codes |
| `tests/` | Cases, fixtures (FIXTURE_ONLY, RFC 5737 addresses), bash tests, Pester parity tests, KQL parse, `run_all.sh` gates |

## Hunts (KQL)

| ID | Label | What it looks for | Tables |
|---|---|---|---|
| Q1a | INVENTORY (VENDOR model list) | Defender discovered devices whose model is in Zyxel's tables | DeviceInfo |
| Q1b | INVENTORY (VENDOR CVE IDs) | Vulnerability management findings for either CVE | DeviceTvmSoftwareVulnerabilities |
| Q2a | OUR PATTERN | Inbound internet traffic to a device admin port (inventory parameter CpeWanIPs is OUR) | CommonSecurityLog |
| Q2b | OUR PATTERN | Managed endpoints reaching a device web UI on the LAN side | DeviceNetworkEvents |
| Q3 | OUR PATTERN | Oversized or malformed HTTP requests to a device web UI (OUR thresholds; no URI paths) | CommonSecurityLog |
| Q4 | OUR PATTERN | A Description parameter with shell metacharacters (the only parameter Zyxel names) | CommonSecurityLog |
| Q4b | OUR PATTERN | The same on proxy lines forwarded as Syslog (UNVERIFIED log formats) | Syslog |
| Q5 | OUR PATTERN | New outbound connections from a device's own address to public destinations | CommonSecurityLog |
| Q6 | OUR PATTERN | DNS, config, account, login, reboot or firmware events from devices (UNVERIFIED log formats) | Syslog |

Ports 80 and 443 in Q2a, Q2b and the Sigma rules are HTTP and HTTPS defaults (OUR assumption); Zyxel publishes no port. Replace
them, and every FIXTURE_ONLY RFC 5737 address, with your own values.

## Sigma rules

| Rule | Label | Level |
|---|---|---|
| `firewall_zyxel_cpe_admin_port_inbound_from_internet.yml` | OUR PATTERN | medium |
| `firewall_zyxel_cpe_device_outbound_public.yml` | OUR PATTERN | low |
| `proxy_zyxel_cpe_description_param_shell_metachar.yml` | OUR PATTERN | high |
| `proxy_zyxel_cpe_oversized_uri.yml` | OUR PATTERN | medium |
| `net_connection_win_zyxel_cpe_web_ui_access.yml` | OUR PATTERN | low |

Conversions (sigma convert -t kusto): no pipeline converts all 5. microsoft_xdr and microsoft_365_defender convert 1 rule, with 4
documented gaps (no firewall or proxy table). sentinel_asim converts 3, with 2 documented gaps (no firewall table).
azure_monitor converts 1, with 4 documented gaps (no firewall or proxy table). For a gap, use the matching KQL hunt.

## Checker

`scripts/check-zyxel-cpe-ont.sh` (bash) and `scripts/Check-ZyxelCpeOnt.ps1` (PowerShell 7) give identical output and exit codes.
Offline only: no network, no device contact, no writes, nothing run. They print only the model, the parsed firmware and an
optional sanitised name; other CSV columns (passwords, serials) are never read into the output.

```
check-zyxel-cpe-ont.sh --model DX3301-T0 --firmware "5.50(ABVY.8.3)C0" [--isp] [--name home-01]
check-zyxel-cpe-ont.sh --inventory devices.csv    # header: model,firmware[,name][,supplied_by]
```

Verdicts per device: AFFECTED, FIXED, UNKNOWN (ISP-supplied, unreadable model or firmware, another firmware line, or a build not
in Zyxel's table) and NOT LISTED (model not in either table). A device marked ISP-supplied (`--isp`, or `supplied_by` = isp) is
always UNKNOWN, with advice to check with the ISP, because Zyxel's tables exclude ISP-customised models.

Exit codes: 0 every device FIXED; 1 any AFFECTED; 3 any UNKNOWN (or no devices), none AFFECTED; 5 only FIXED and NOT LISTED
devices (review); 4 usage, input or data file error.

## Unverified items

- How Defender device discovery fills Vendor and Model for these devices (Q1a).
- Field names for HTTP data in CommonSecurityLog and the proxy line format in Syslog (Q3, Q4, Q4b).
- Every Syslog keyword in Q6: Zyxel publishes no log format.
- Whether builds earlier than the one Zyxel lists in Table 2 are affected by CVE-2026-86676 (the checker reports UNKNOWN).
- Admin ports 80 and 443 (OUR assumption).

## Corrections to the brief

- Table 1 lists 48 models for CVE-2026-79614 and Table 2 lists 30 for CVE-2026-86676; there are 49 distinct models in total.
- Table 2 names exact builds, not "and earlier" ranges.
- CVE-2026-86676 is CWE-78, rated 7.2 High by the CNA (shown on NVD; no NVD score yet), so this pack rates it High.
- "No exploitation reported": Zyxel's advisory says nothing about exploitation either way; what we verified is that neither CVE
  is in CISA KEV.
- Zyxel names the researchers; this pack credits "security researchers" only.

## Advisory state at finish

Zyxel advisory: revision history "2026-11-17: Initial release". NVD: both records "Received". KEV catalog 2026.11.13: neither
CVE listed. Read 17 Nov 2026 02:30 GMT.

## Sources

- Zyxel security advisory, 17 Nov 2026: https://www.zyxel.com/global/en/support/security-advisories/zyxel-security-advisory-for-out-of-bounds-write-and-post-authentication-command-injection-vulnerabilities-in-certain-dsl-ethernet-cpe-fiber-onts-and-wireless-extenders-11-17-2026
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-79614 and https://nvd.nist.gov/vuln/detail/CVE-2026-86676
- cve.org: https://www.cve.org/CVERecord?id=CVE-2026-79614 and https://www.cve.org/CVERecord?id=CVE-2026-86676
- CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- MITRE ATT&CK: https://attack.mitre.org/techniques/T1190/ and https://attack.mitre.org/techniques/T1059/004/
- MITRE CWE: https://cwe.mitre.org/data/definitions/787.html and https://cwe.mitre.org/data/definitions/78.html

See CHANGELOG.md for versions.
