Release ASUS TUF-AX6000 Firmware version 3.0.0.4.388_33965 (2025/10/23)

[Tech9]

I'm on firmware 3.0.0.4.388_31374-g617d05c

This firmware is not available for download anymore though. In ASUS world this means there is newer minimum required firmware version for this model router. Going back is not recommended.

I have switched off the firmware updates to be sure that it won't update by himself.

It may still auto upgrade (very likely) according to ASUS documents. It was made official some time ago ASUS reserves the right to auto upgrade firmware when minimum required firmware version changes.

 

[denis]

Hi and thank you for your feedback.

The latest stable version that has been recommended over here (but without extensive testing) is TUF-AX6000_3.0.0.4_388_33427-gc525e4e.

Any specific reason why you chose 3.0.0.4.388_31374-g617d05c and/or how did you choose that specific version?

Glad you found a stable setup. Any clue regarding possible security risks?
Thanks!

I have choose one of the earliest firmware.
I know that it might be a bit risky.
But I'm not enabling

This firmware is not available for download anymore though. In ASUS world this means there is newer minimum required firmware version for this model router.



It may still auto upgrade according to ASUS documents. It was made official some time ago ASUS reserves the right to auto upgrade firmware when minimum required firmware version changes.

It was not pushed a force upgrade.
In 71 days it is long enough....
Considering the firmware is from 2023.
Maybe because I didn't agree to their terms and conditions inside firmware.
It's in there a paragraph that states if I am not accepting the t&c I'm not able to receive latest updates.
Could be that or could be they know that they have an problematic firmware.
Anyway I'm happy that I can use the hardware for the purpose I bought it.
Ah,regarding security....
Got a 30 number/letter passwords everywhere on it.
But if someone want and have the knowledge it might get in.
Nothing is unbreakable these days.

 

[Tech9]

Life is tough with this TUF. For some reason ASUS have issues with MediaTek devices. They had some budget ones in AC-class and they were short lived reaching EoL faster than others.

 

[UltrashRicco]

This firmware is not available for download anymore though. In ASUS world this means there is newer minimum required firmware version for this model router. Going back is not recommended.



It may still auto upgrade (very likely) according to ASUS documents. It was made official some time ago ASUS reserves the right to auto upgrade firmware when minimum required firmware version changes.

Most, if not all legacy firmwares are retrievable from the Internet Archive.

This page below, from July 2024, lists 8 releases including the very first one (3.0.0.4.388.31374 from 05/01/2023, your current version) and up to 3.0.0.4.388_33405 (28/05/2024). Then the current Asus website hosts FWs from 3.0.0.4.388_33419 (15/10/2024) onwards.

TUF Gaming AX6000｜WiFi Routers｜ASUS Global

TUF Gaming AX6000 Dual Band WiFi 6 Gaming Router with dedicated Gaming Port, Dual 2.5G Port, 3steps port forwarding, AiMesh for mesh WiFi, AiProtection Pro network security and AURA RGB lighting.

web.archive.org

Quite a few CVE security vulnerabilities were fixed over 2023 and 2024, you should read the changelogs/release notes @denis and try and understand whether your current version is vulnerable to a remote attack.
Perhaps you should consider switching to 3.0.0.4.388_33427 (06/11/2024) which is the last known trouble-free version (at least regarding slow page loading over WiFi), with many security uptades contrary to the initial release version that you are currently running (3.0.0.4.388.31374).

I would suggest running at least 3.0.0.4.388_33405 from 28/05/2024, as subsequent updates did not incorporate major security fixes.

 

[Metroguy]

Guys , I have the a problem on the good .427 firmware as well where the webpages in chrome on my Android mobile phone will show a can't be reached page , the subsequently reloads and gets loaded. Not sure if this problem is related to that people are discussing in this topic. But I recalled fiddling with settings a whole ago


I think the issue is related to qos and nat acceleration. Disabling qos and setting nat acceleration to auto seems to have solved it . Have to wait and see if the problem comes back

So I believe since qos is related to CPU functions the bug is with the mediatek code probably as someone stated earlier