CVE-2025-6599 — Uncontrolled Resource Consumption in Zyxel Ax7501-b0 Firmware
An uncontrolled resource consumption vulnerability in the web server of Zyxel DX3301-T0 firmware version 5.50(ABVY.6.3)C0 and earlier could allow an attacker to perform Slowloris‑style denial‑of‑service (DoS) attacks. Such attacks may temporarily block legitimate HTTP requests and partially disrupt access to the web management interface, while other networking services remain unaffected.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.3% (30-day exploitation probability)+3
- Technical severity (high)+6
- Automatable exploitation (SSVC)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Zyxel Ax7501-b0 Firmware, Zyxel Ax7501-b1 Firmware, Zyxel Dm4200-b0 Firmware…).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes matching the vulnerability class (denial of service), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Zyxel | Ax7501-b0 Firmware | ≤ 5.17\(abpc.6.1\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Ax7501-b1 Firmware | ≤ 5.17\(abpc.6.1\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Dm4200-b0 Firmware | ≤ 5.17\(acbs.1.3\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Dx3300-t0 Firmware | ≤ 5.50\(abvy.6.3\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Dx3300-t1 Firmware | ≤ 5.50\(abvy.6.3\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Dx3301-t0 Firmware | version <= 5.50(ABVY.6.3)C0 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Zyxel | Dx3301-t0 Firmware | ≤ 5.50\(abvy.6.3\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Dx4510-b1 Firmware | ≤ 5.17\(abyl.9\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Dx5401-b0 Firmware | ≤ 5.17\(abyo.7\)b2 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Dx5401-b1 Firmware | ≤ 5.17\(abyo.7\)b2 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Ee3301-00 Firmware | ≤ 5.63\(acmu.1.1\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Ee5301-00 Firmware | ≤ 5.63\(acld.1.1\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Ee6510-10 Firmware | ≤ 5.19\(acjq.3\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Emg3525-t50b Firmware | ≤ 5.50\(abpm.9.5\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Emg5523-t50b Firmware | ≤ 5.50\(abpm.9.5\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Emg5723-t50k Firmware | ≤ 5.50\(abom.8.6\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Emg6726-b10a Firmware | ≤ 5.13\(abnp.8\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Ex3300-t0 Firmware | ≤ 5.50\(abvy.6.3\)c0≤ 5.50\(acdi.2.1\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Ex3300-t1 Firmware | ≤ 5.50\(abvy.6.3\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Ex3301-t0 Firmware | ≤ 5.50\(abvy.6.3\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Ex3500-t0 Firmware | ≤ 5.44\(achr.4\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Ex3501-t0 Firmware | ≤ 5.44\(achr.4\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Ex3600-t0 Firmware | ≤ 5.70\(acif.1.2\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Ex5401-b0 Firmware | ≤ 5.17\(abyo.7\)b2 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Ex5401-b1 Firmware | ≤ 5.17\(abyo.7\)b2 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Ex5501-b0 Firmware | ≤ 5.17\(abry.5.5\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Ex5510-b0 Firmware | ≤ 5.17\(abqx.10\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Ex5512-t0 Firmware | ≤ 5.70\(aceg.5\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Ex5601-t0 Firmware | ≤ 5.70\(acdz.4.1\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Ex5601-t1 Firmware | ≤ 5.70\(acdz.4.1\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Ex7501-b0 Firmware | ≤ 5.18\(achn.2.1\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Ex7710-b0 Firmware | ≤ 5.18\(acak.1.4\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Gm4100-b0 Firmware | ≤ 5.18\(accl.1\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Lte3301-plus Firmware | ≤ 1.00\(abqu.7\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Nebula Fwa505 Firmware | ≤ 1.19\(acko.0\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Nebula Fwa510 Firmware | ≤ 1.20\(acgd.1\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Nebula Fwa515 Firmware | ≤ 1.50\(acpz.0\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Nebula Fwa710 Firmware | ≤ 1.20\(acgc.0\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Nr5103 Firmware | ≤ 4.19\(abyc.8\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Nr5103e Firmware | ≤ 1.00\(acdj.1\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Nr5309 Firmware | ≤ 1.00\(ackp.1\)b3 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Nr7302 Firmware | ≤ 5.00\(acha.5\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Nr7303 Firmware | ≤ 1.00\(acei.1\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Pe3301-00 Firmware | ≤ 5.63\(acmt.1.1\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Pe5301-01 Firmware | ≤ 5.63\(acoj.1.1\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Pm3100-t0 Firmware | ≤ 5.42\(acbf.3\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Pm5100-t0 Firmware | ≤ 5.42\(acbf.3\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Pm7300-t0 Firmware | ≤ 5.42\(abyy.3\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Pm7500-00 Firmware | ≤ 5.61\(ackk.1\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Px3321-t1 Firmware | ≤ 5.44\(achk.1\)c0≤ 5.44\(acjb.1.3\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Px5301-t0 Firmware | ≤ 5.44\(ackb.0.4\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Scr 50axe Firmware | ≤ 1.10\(acgn.3\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Vmg3625-t50b Firmware | ≤ 5.50\(abpm.9.5\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Vmg3927-b50b Firmware | ≤ 5.13\(ably.10\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Vmg3927-t50k Firmware | ≤ 5.50\(abom.8.6\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Vmg4005-b50a Firmware | ≤ 5.17\(abqa.3\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Vmg4005-b50b Firmware | ≤ 5.13\(abrl.5.3\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Vmg4005-b60a Firmware | ≤ 5.17\(abqa.3\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Vmg4927-b50a Firmware | ≤ 5.13\(ably.10\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Vmg8623-t50b Firmware | ≤ 5.50\(abpm.9.5\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Vmg8825-t50k Firmware | ≤ 5.50\(abom.8.6\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | We3300-00 Firmware | ≤ 5.70\(acka.0\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Wx3100-t0 Firmware | ≤ 5.50\(abvl.4.7\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Wx3401-b0 Firmware | ≤ 5.17\(abve.2.8\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Wx3401-b1 Firmware | ≤ 5.17\(abve.2.8\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Wx5600-t0 Firmware | ≤ 5.70\(aceb.4.1\)c0 | Vulnerable | NIST National Vulnerability Database |
| Zyxel | Wx5610-b0 Firmware | ≤ 5.18\(acgj.0.3\)c0 | Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 7.5 | CVSS 3.1 | High | 3.9 | 3.6 | nvd@nist.gov via NIST National Vulnerability Database |
| 5.3 | CVSS 3.1 | Medium | 3.9 | 1.4 | security@zyxel.com.tw via NIST National Vulnerability Database |
| 5.3 | CVSS 3.1 | Medium | — | — | Zyxel via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.31%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Track CPU/memory spikes and availability drops correlated with request patterns.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · zyxel/dx3301-t0 firmware
- SSVC assessment updated
- Record published
- CVSS changed · 7.5
- Source status changed · → Analyzed
- Record created in this database
- 2025
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
1 on the record
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-1460 OS Command Injection in Zyxel Nebula Fwa70 Firmware Apr 28, 2026
- Medium CVE-2026-0711 OS Command Injection in Zyxel Nr5307 Firmware Apr 28, 2026
- Critical CVE-2025-13942 OS Command Injection in Zyxel Wx5610-b0 Firmware Feb 24, 2026
- Medium CVE-2025-11848 NULL Pointer Dereference in Zyxel Ex5601-t1 Firmware Feb 24, 2026
- High CVE-2025-13943 OS Command Injection in Zyxel Ex5601-t1 Firmware Feb 24, 2026
- High CVE-2026-1459 OS Command Injection in Zyxel Vmg3625-t50c Firmware Feb 24, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2025-6599 is "Uncontrolled Resource Consumption in Zyxel Ax7501-b0 Firmware", rated High. It affects Ax7501-b0 Firmware (Zyxel); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.5 describes technical severity. EPSS 0.31% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.