🛡️ CVE-2026-7255 — wre6505-firmware

How this vulnerability can be exploited

This issue can be reached from an adjacent network, attack complexity is low, an attacker needs no privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality high, integrity none, availability none.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

• Attack vector: Adjacent network — the attacker has to sit on the same local or logical network.
• Attack complexity: Low — the attack works reliably, with no preparation.
• Privileges required: None — an unauthenticated stranger can try it.
• User interaction: None — nobody has to be tricked into anything.
• Scope: Unchanged — the damage stays inside the vulnerable component.
• Confidentiality impact: High — total loss, or loss the attacker controls.
• Integrity impact: None.
• Availability impact: None.

Weakness class

CVE-2026-7255 is classified as CWE-307: Improper Restriction of Excessive Authentication Attempts. Repeated login attempts are not limited, leaving credentials open to brute forcing.

Affected software

CVE-2026-7255 is recorded against 1 package.

• wre6505-firmware

Timeline and source

Published on 12 May 2026 and last revised on 17 June 2026. No public exploit is currently recorded for this entry. Record sourced from NVD.

References

www.zyxel.com

Other advisories for this package

wre6505-firmware has other advisories on record. If you are patching this one, these are worth checking on the same host:

• CVE-2026-7257 (4.4 Medium, published 12 May 2026)
• CVE-2026-7256 (8.8 High, published 12 May 2026)
• CVE-2026-6058 (4.5 Medium, published 21 Apr 2026)

Same weakness in other software

These advisories are the same class of weakness (CWE-307: Improper Restriction of Excessive Authentication Attempts) in other software:

• CVE-2026-65948 (7.3 High, published 10 Aug 2026)
• CVE-2026-16619 (7.5 High, published 6 Aug 2026)
• CVE-2026-48084 (7.4 High, published 6 Aug 2026)
• CVE-2026-48071 (5.8 Medium, published 6 Aug 2026)
• CVE-2026-71213 (9.1 Critical, published 5 Aug 2026)
• CVE-2026-71205 (6.5 Medium, published 5 Aug 2026)
• CVE-2026-8793 (published 3 Aug 2026)
• CVE-2026-15144 (7.3 High, published 29 Jul 2026)

Details

Affected Packages

References