[Release Note] Zyxel AX/AXE series Access Point - V7.10 Patch 4 firmware has been released

Zyxel_Melen · January 22

AX/AXE series Access Points Firmware Release Note

January 2026

Overview

This document provides firmware release information on Zyxel Access Points platforms, introduce new Access Points, new features and enhancements, bug fix, known issues and workarounds information for Release V7.10 Patch 4 C0.

Supported Platforms

(Click Hyperlink to download the firmware directly)

WiFi 6E model(s):

Zyxel WAX640S-6E - V7.10(ACCM.4)C0

Zyxel WAX620D-6E - V7.10(ACCN.4)C0

Zyxel NWA220AX-6E - V7.10(ACCO.4)C0

WiFi 6 model(s):

Zyxel WAX655E - V7.10(ACDO.4)C0

Zyxel WAX650S - V7.10(ABRM.4)C0

Zyxel WAX630S - V7.10(ABZD.4)C0

Zyxel WAX610D - V7.10(ABTE.4)C0

Zyxel WAX510D - V7.10(ABTF.4)C0

Zyxel WAX300H - V7.10(ACHF.4)C0

Zyxel NWA210AX - V7.10(ABTD.4)C0

Zyxel NWA110AX - V7.10(ABTG.4)C0

Zyxel NWA90AX PRO - V7.10(ACGF.4)C0

Zyxel NWA50AX PRO - V7.10(ACGE.4)C0

Zyxel NWA50AX - V7.10(ABYW.4)C0

Zyxel NWA55AXE - V7.10(ABZL.4)C0

Zyxel NWA90AX - V7.10(ACCV.4)C0

Zyxel NWA55AX PRO - V7.10(ACSP.4) (first firmware version)

Zyxel NWA55AX PTP - V7.10(ACSQ.4) (first firmware version)

New Features and Enhancements

1. Captive Portal Security: Enables Two-Factor Authentication (2FA) for Captive Portal logins using the Nebula Cloud Authentication Server (NCAS).
Note: This feature currently does not support External Portal configurations.

2. Dynamic Bandwidth Control: Administrators can now apply client rate limits dynamically using RADIUS attributes.

Bug Fix

C=Cloud mode, M=Managed, S=Standalone mode

Bug fix	C	M	S
1. [eITS: 251101963] [Symptom] After rebooting the USG FLEX H series, managed access points may incorrectly display a “VLAN Conflict” status in the AP list, even though the VLAN configuration is correct.	-	V	-
2. [eITS: 250900495, 251000461, 251001277, 251001391, 251101547] [Symptom] The AP experienced unexpected reboot events, with the event log showing “Reboot by wireless auto recovery process. IP: 0.0.0.0.”	V	V	V
3. [RMID: 64851] [Symptom] When the “Permit access to Nebula devices exclusively from designated IP addresses” setting is enabled, an access point may become temporarily inaccessible via the local GUI after being removed from a Nebula organization and switched to standalone mode.	V	-	-

Known Issue

C=Cloud mode, M=Managed, S=Standalone mode

Known Issue	C	M	S
1. [eITS: 250401445] [Symptom] VLAN and Security fields in the clients list display incorrect values when 802.1x MAC authentication with VLAN assignment is used.	V	-	-
2. [RMID: 66723] [Symptom] When using Nebula Captive Portal with an internal or external RADIUS server, the SSID on the NWA55AX PRO / PTP access point may unexpectedly go down after the configuration is applied.	V	V	V

Limitation of Settings

N/A

Nakatomi_Uk · January 22

Sorry for the very late reply, if I want to change to Nebular mode do I go into my Zynel router (provided by my ISP) and add the firewall settings to open the ports for it? is that all I need to do

Zyxel_Melen · January 23

https://community.zyxel.com/en/discussion/comment/83051#Comment_83051

Please check the reply in your post.

Pbee · January 23

The WPA3/SAE issue with Apple devices still exists in this version.

2) after reboot of the AP, I see this line in the log:

msg="System event dhcp6c occurred from WAX650S" note="CoredumpApp"

[ 78.389474] dhcp6c[5895]: unhandled level 0 translation fault (11) at 0x17076972cd80, esr 0x92000004

The unit does get the expected IPv6 addresses and keeps on running for weeks/months without issues afterwards. (Router pfSense, configured with priority for DHCPv6)
When I look in the internal storage, all coredumps found are since version 7.10-ABRM.1 after every reboot/power on.

dmesg.txt

Note that we do not reboot periodically, nor do we see spontaneous reboots. Only after a firmware update. We let the AP just run continuously.

Jason95357 · January 29

v7.10p4 has a problem with NWA50AX PRO and Pixel 9a. The Pixel 9a will say it cannot connect and to check the password after a number of attempts. Logs on the AP show "blocked by key handshake fail". Reverting to v7.10p3 resolves the problem.