.On Firebox T115-W, T125, T125-W, T145, and T145-W devices, you can now again assign VLAN ID 1 to any interface for either tagged or untagged VLANs. This removes the VLAN 1 restriction introduced in Fireware v2026.1.2. The Firebox now reserves VLAN ID 4094 for internal switch use, and you can select any VLAN ID from 1 to 4093 for tagged or untagged VLANs. If you previously configured VLAN ID 4094 on these devices, you must change that VLAN to a different VLAN ID after you upgrade to Fireware v2026.2. [FBX-32130]

Fixes 2 Security Issues plus other bugs

What can I do to get even the second one on 2026.1?

Thanks and regards,
Chris

For Firebox models: T115-W, T125, T145, T185, M295, M395, M495, M595, M695

Seems that one of our customers was hit by an attack even a few hours before we got the notification about an available update from WG.

Would a reset to factory defaults clean the box so that it can be reused safely after that or what else is recommended in this case by WG?

This email is to inform you that we have released new Firebox firmware that patches a critical security flaw.

Through internal investigation, WatchGuard has identified a new critical Fireware OS vulnerability in the IKEv2 VPN service, affecting all Firebox models and versions; and a patch is now available from our Software Downloads center. Threat actors are attempting to exploit this vulnerability as part of a wider attack campaign against edge networking equipment and exposed infrastructure from multiple vendors. Therefore, we urge you to immediately upgrade any Firebox appliances that you own or manage, and proactively communicate with customers about the Firebox upgrade.

We have reserved CVE-2025-14773 for this vulnerability. For specific information on the vulnerability, mitigation guidance, and resolution, please consult the Security Advisory (WGSA-2025-0027), which we have published in accordance with our responsible disclosure process.

The following new firmware versions are available as of 18 December 2025, to update your Firebox appliance(s):
• Fireware 2025.1.4 or higher
• Fireware v12.11.6 or higher
• Fireware v12.5.15 or higher
• Fireware v12.3.1 Update 4 or higher
Given that this vulnerability is being exploited, we have sent this email as soon as possible to inform you of the patch availability. We expect this information may be syndicated through cybersecurity trade publications and threat research organizations, further necessitating a fast response and proactive communication with your clients.
If you have any further questions, contact WatchGuard Support or your WatchGuard account representative.

I used to upgrade the cluster manually but do upgrade other stand alone firewalls using cloud and it has been working fine so far.
So now I want to try upgrade the cluseter as well.

Final question, when I schedule a upgrade using cloud - is it possible to see it somewhere and also stop it if I for some reason regret the scheduled upgrade?

/Martin

On the Fireware Web UI Front Panel page, the System section now shows a notification when a new version of Fireware is available.

Plus fixes etc.

M370 running 12.6.2 logs this quite often:

Archived log file /var/log/traffic.log which reached max size

An error occured while refreshing "Front Panel":
java.lang.NumberFormatException: For input string: "Wed Jan 3 19:05:21 2024"

The time/date matches upgrade time...
I do not have Java installed on management server (it was removed earlier as it is not free anymore).

We have currently a T30W which is out of support, and so our IT company were badgering us to upgrade.

We have also just had our incoming fibre leased line speed increased and the existing T30 is unable to handle the new speed. We are based in the UK.

We have therefore purchased a new T45W, but our IT company are unable to book in the install for approx. 6 weeks.

I have read the guides and have exported an XML file, and searched and changed references of T30 to T45, and have uploaded it to the Watchguard portal, and I have connected the box using an existing network port and then to my computer. I can access the web UI, I also managed to obtain the Feature Serial key, but I don't seem to be able to get the previous XML file imported.

The incoming service which would normally feed directly into the firebox is on a fixed IP and the "router" does not handle DHCP, should this be the information I add during the setup wizard?

Sorry for long post, but if anyone is able to provide any links or help or if you are able to advise how to set up without internet connection it would be appreciated.