cve.bz

CVE-2026-7255 zyxel wre6505 firmware

6.5 mediumEPSS 0.2%Unsupported when assigned

Medium (6.5) in zyxel wre6505 firmware. No vendor fix: the product was unsupported when the CVE was assigned. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
An improper restriction of excessive authentication attempts vulnerability in the web management interface of Zyxel WRE6505 v2 firmware version V1.00(ABDV.3)C0 could allow an adjacent attacker on the LAN to brute-force the password and bypass authentication.

Severity

CVSS 3.1

6.5 medium
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
0.2% (unchanged from 0.2% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 10th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-05-12. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-307 Improper Restriction of Excessive Authentication Attempts
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-7255 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-7255?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-7255?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-7255 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-7255

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-7255](https://cve.bz/cve/badge/CVE-2026-7255.svg)](https://cve.bz/cve/CVE-2026-7255)

HTML:

<a href="https://cve.bz/cve/CVE-2026-7255"><img src="https://cve.bz/cve/badge/CVE-2026-7255.svg" alt="CVE-2026-7255"></a>

Affected

Versions

From the NVD's CPE matches.

ProductAffected
zyxel:wre6505_firmwarev1.00(abdv.3)c0

Attack patterns (CAPEC)

  • CAPEC-16 Dictionary-based Password Attack Likelihood: Medium · Severity: High
  • CAPEC-49 Password Brute Forcing Likelihood: Medium · Severity: High
  • CAPEC-560 Use of Known Domain Credentials Likelihood: High · Severity: High
  • CAPEC-565 Password Spraying Likelihood: High · Severity: High
  • CAPEC-600 Credential Stuffing Likelihood: High · Severity: High
  • CAPEC-652 Use of Known Kerberos Credentials Likelihood: Medium · Severity: High
  • CAPEC-653 Use of Known Operating System Credentials Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON