CVE-2026-1459
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA post-authentication command injection vulnerability in the TR-369 certificate download CGI program of the Zyxel VMG3625-T50B firmware versions through 5.50(ABPM.9.7)C0 could allow an authenticated attacker with administrator privileges to execute operating system (OS) commands on an affected device.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA command injection vulnerability exists in the TR-369 certificate download CGI program of Zyxel VMG3625-T50B routers. An authenticated attacker with administrator privileges can inject and execute arbitrary OS commands through unsanitized input in the certificate download functionality.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 5.50\(abpm.9.7\)c0<= 5.50\(abpm.9.7\)c0<= 5.50\(abpm.9.7\)c0<= 5.50\(abpm.9.7\)c0<= 5.17\(abyo.7.1\)c0<= 5.50\(abpm.9.7\)c0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelCheck the router model label or login to the admin interface and locate the model number typically displayed on the dashboard or status pageAffected if The model is VMG3625-T50B, VMG3625-T50C, EMG5523-T50B, EMG3525-T50B, DX5401-B1, or VMG8623-T50B
-
Check the installed firmware versionLog into the router admin interface and navigate to the firmware version or system status page. Compare the displayed version against 5.50(abpm.9.7)c0 for T50x models or 5.17(abyo.7.1)c0 for DX5401-B1Affected if The firmware version is 5.50(abpm.9.7)c0 or lower for T50x models, or 5.17(abyo.7.1)c0 or lower for DX5401-B1
-
Verify TR-369 web interface accessibilityAttempt to access the TR-369 /cgi-bin/luci/certificate download endpoint or check if the web interface is reachable on the default HTTP/HTTPS ports (80/443)Affected if The router web management interface is exposed and accessible from the network being assessed
-
Review admin access logs for suspicious activityCheck router logs, especially authentication and administrative action logs, for unexpected administrator sessions or unusual command execution entries around the certificate download functionalityAffected if There are log entries showing certificate download actions initiated from unexpected IP addresses or at times when no legitimate admin was logged in
The device is affected if it is one of the listed models running firmware at or below the specified version and the TR-369 administrative interface is accessible.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the latest firmware patch from Zyxel when available. If no patch exists, restrict administrative access to trusted IP addresses and monitor for unauthorized administrative sessions.
- Consultation4.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1459 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-1459 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data