CVE
Zyxel DX3301-T0 firmware unauthenticated code execution in libclinkc.so
Affects Zyxel DX3301-T0 and EX3301-T0 firmware through 5.50(ABVY.8.3)C0 when WAN access is enabled. No fixed version is listed in the checked facts.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Exploited
- No known exploitation
- Fix
- See vendor advisory
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Firmware version 5.50(ABVY.8.3)C0 and earlier on the DX3301-T0 or EX3301-T0. WAN access enabled on the device, since WAN access is disabled by default.
- Published
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 27/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
An out-of-bounds write vulnerability in “libclinkc.so” in Zyxel DX3301-T0/EX3301-T0 firmware versions through 5.50(ABVY.8.3)C0 could allow an unauthenticated attacker to elevate privileges and potentially execute arbitrary commands by sending a crafted HTTP request. WAN access is disabled by default on these devices.
Who should check
Anyone running Zyxel DX3301-T0 or EX3301-T0 firmware 5.50(ABVY.8.3)C0 or earlier with WAN access enabled.
“5.50(ABVY.8.3)C0 and earlier”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure12/25Specific setups only, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.8/10CVSS 9.8
- No patch5/5No fixed version listed; see vendor advisory
What would change the score
- Would score about 77 if added to CISA KEV
- Would score about 72 if CISA's SSVC rates exploitation active
What to do
Check whether your setup matches what the bug needs.
Firmware version 5.50(ABVY.8.3)C0 and earlier on the DX3301-T0 or EX3301-T0. WAN access enabled on the device, since WAN access is disabled by default.Workaround: Since no fix is listed, limit the exposure by keeping WAN access disabled, which is the default setting on these devices.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-79614 (An out-of-bounds write vulnerability in “libclinkc.so” in Zyxel DX3301-T0/EX3301-T0 firmware versions through 5.50(ABVY.8.3)C0 could allow…), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-79614 (entry last updated 2026-11-17):
Affected:
- Zyxel DX3301-T0 firmware: through 5.50(ABVY.8.3)C0
- Zyxel EX3301-T0 firmware: through 5.50(ABVY.8.3)C0
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Firmware version 5.50(ABVY.8.3)C0 and earlier on the DX3301-T0 or EX3301-T0. (source: 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)
- WAN access enabled on the device, since WAN access is disabled by default. (source: 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)
Setup: the bug needs a feature or setting that is off by default or uncommon. Check whether each asset has it on.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-79614 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-79614 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- 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
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-79614
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-79614"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- Zyxel DX3301-T0 firmware
through 5.50(ABVY.8.3)C0
- Zyxel EX3301-T0 firmware
through 5.50(ABVY.8.3)C0
Evidence 3
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-79614
Is CVE-2026-79614 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
An out-of-bounds write in the libclinkc.so library can let an unauthenticated attacker elevate privileges and potentially execute arbitrary commands on the device.Source: zyxel.com
Which versions are affected by CVE-2026-79614?
DX3301-T0 firmware: through 5.50(ABVY.8.3)C0. EX3301-T0 firmware: through 5.50(ABVY.8.3)C0.Source: cve.now feed data
Am I affected, and how do I check?
Firmware 5.50(ABVY.8.3)C0 and earlier on the DX3301-T0 or EX3301-T0 is in scope, and the issue applies only when WAN access is enabled, since WAN access is disabled by default. Check the firmware version and the WAN access setting on the device.Source: zyxel.com
How do I fix CVE-2026-79614?
The checked facts do not name a fixed version or patch, so no upgrade target can be given from them. Check Zyxel's advisory for a fix.Source: zyxel.com
What if there's no patch?
Since no fix is listed, limit the exposure by keeping WAN access disabled, which is the default setting on these devices.Source: zyxel.com