CVE
Zyxel DX3300-T0 firmware OS command injection in CGI description parameter
Zyxel DX3300-T0 firmware up to and including 5.50(ABVY.8.3)C0 is affected, and the attack requires WAN access to be enabled along with compromised administrator credentials.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
CVSS:3.1/AV:N/AC:L/PR:H/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. WAN access enabled on the device, since it is disabled by default Attacker must hold administrator credentials, which requires user-configured passwords to be compromised
- 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? →
- 20/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
Zyxel DX3300-T0 firmware has a command injection flaw in the "Description" parameter of a CGI program. An attacker with administrator privileges can use it to run operating system commands on the device. The attacker can reach the flaw remotely over the network by sending a crafted HTTP request, but must first log in with administrator credentials.
Original description
A post-authentication command injection vulnerability in the “Description” parameter of a CGI program in Zyxel DX3300-T0 firmware versions through 5.50(ABVY.8.3)C0 could allow an authenticated attacker with administrator privileges to execute OS commands by sending a crafted HTTP request.
Who should check
Teams running Zyxel DX3300-T0 firmware through 5.50(ABVY.8.3)C0 with WAN access enabled, including Zyxel DX-series and related DSL/Ethernet CPE, Fiber ONT and extender models listed by Zyxel
“Table 2. Models affected by CVE-2026-86676”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.2/10CVSS 7.2
- No patch5/5No fixed version listed; see vendor advisory
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
- Would score about 27 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
WAN access enabled on the device, since it is disabled by default Attacker must hold administrator credentials, which requires user-configured passwords to be compromisedWorkaround: Keep WAN access disabled, which is the default, and use strong administrator passwords, since the attack can succeed only if user-configured passwords have been compromised.
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-86676 (A post-authentication command injection vulnerability in the “Description” parameter of a CGI program in Zyxel DX3300-T0 firmware versions…), 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-86676 (entry last updated 2026-11-17):
Affected:
- Zyxel DX3300-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):
- WAN access enabled on the device, since it 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)
- Attacker must hold administrator credentials, which requires user-configured passwords to be compromised (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, high-privilege login, no user action.
CISA KEV: CVE-2026-86676 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-86676 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-86676
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-86676"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- Zyxel DX3300-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-86676
Is CVE-2026-86676 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?
A crafted HTTP request sent to the Description parameter of a CGI program lets an authenticated administrator run operating system commands on the device.Source: zyxel.com
Which versions are affected by CVE-2026-86676?
DX3300-T0 firmware: through 5.50(ABVY.8.3)C0.Source: cve.now feed data
Am I affected, and how do I check?
DX3300-T0 firmware up to and including 5.50(ABVY.8.3)C0 is in the affected range. WAN access is disabled by default, so the setup depends on whether WAN access has been enabled, and the attacker must hold administrator credentials.Source: zyxel.com
How do I fix CVE-2026-86676?
The available facts do not name a fixed firmware version or vendor patch, so check Zyxel's advisory for an update before relying on any particular version.Source: zyxel.com
What if there's no patch?
Keep WAN access disabled, which is the default, and use strong administrator passwords, since the attack can succeed only if user-configured passwords have been compromised.Source: zyxel.com