Unraid 7.3.1 is now stable. Read the full announcement on the Unraid blog.

For step-by-step upgrade instructions, see Updating Unraid.

Release Highlights

Security

• Updated nginx (1.30.1) to address 13 CVEs

• Updated bind (9.20.23) to address 9 CVEs

• Updated rsync (3.4.3) to address 6 CVEs

• Updated dnsmasq (2.92rel2) to address 6 CVEs

• Updated avahi, glibc, and jq with NVD-referenced security fixes

• Updated Docker to 29.5.1, including upstream Docker CVE fixes

Linux Kernel

• Update to 6.18.33-Unraid

Docker

• Docker engine updated to 29.5.1

• Fix: Docker container dropdown menu remains usable when many containers are shown

Storage

• Update ZFS to 2.4.2

• Fix: unassigned spare disks now spin down as expected

• Fix: mirrored boot pools can recover from a degraded state after a member device returns for cache pool usage

• Fix: relaxed pool name validity check when importing existing pools to match pre-7.3 validation

• Fix: replacing an online raidz device no longer fails in affected configurations

WebGUI / System

• Fix: restored Connect version-check logic so required updates are detected correctly

• Fix: file uploads now handled correctly on Safari iOS

Networking

• Fix: dhcpcd no longer waits 60 seconds to obtain an IP address on affected systems

Links

• Release Notes

• Blog Post

• Bug Reports

Was waiting for this one. 7.3.0 - 7.3.1 no issue

Updated from 7.3.0 seemingly without issue.

Updated both backup and main servers from 7.3.0 without issue.

Updated three systems from 7.2.7 to 7.3.1 - no issues. Running on USBs. I skipped the config wizard post-reboot on login.

Thanks!

Edited May 28May 28 by ezhik

Although not stated in the release notes, this seems to have fixed the issue of the batteries in certain UPS models not being recognized. My UPS battery is now detected and is working as expected (UPS Model: Back-UPS BE1050G2)

1 minute ago, Yak said:

Although not stated in the release notes, this seems to have fixed the issue of the batteries in certain UPS models not being recognized.

Most likely because it was fixed by the kernel update without LT knowing, since it only happened with a few UPS models.

3 minutes ago, JorgeB said:

Most likely because it was fixed by the kernel update without LT knowing, since it only happened with a few UPS models.

Just thought I'd put it out there in case anyone else running NUT plugin as a workaround wanted to check if the native UPS management was now working for them.

7.3.0 -> 7.3.1 update was smooth as silk. Appreciated, thank you!

4 out of 5 Unraids updated without issues. One (the big boy) has API errors now.

Updated from 7.3.0 - no issues so far 👍

Works flawless

Hello! Thanks so much for the excellent update!

I'd just like to confirm my understanding is correct here. I'm trying to migrate to internal boot. I've run the migration wizard, which said it worked moving to my new internal drives. I saw the waring about switching the boot order, which I didn't change. So now I have the warning "Internal Boot Available".

I'm assuming this means I'm still booting from my original USB. Do I just need to change the boot order in my BIOS? Will the fact that I've been running for 24 hours on the USB after the migration cause any issues?

Edited May 28May 28 by eraser1320

3 hours ago, eraser1320 said:

Hello! Thanks so much for the excellent update!

I'd just like to confirm my understanding is correct here. I'm trying to migrate to internal boot. I've run the migration wizard, which said it worked moving to my new internal drives. I saw the waring about switching the boot order, which I didn't change. So now I have the warning "Internal Boot Available".

I'm assuming this means I'm still booting from my original USB. Do I just need to change the boot order in my BIOS? Will the fact that I've been running for 24 hours on the USB after the migration cause any issues?

Yes, you need to change/verify the boot order in your bios for your internal boot drive to be 1st. Keep in mind you will still need to leave your USB drive for license verification. If you move your license to TPM, and your internal boot drive is successful, you should then be able to remove the USB and use it for something else.

went from 7.2.5 to 7.3.1.

this update makes my linux VM /w intel arc not work. no errors, no clues in the logs just blank "no input" screen.

downgraded as im not in the mood to troubleshoot.

Edited May 28May 28 by Ver7o

FYI: It seems that the Docker Engine got updated to 29.5.2 (29.5.1 is mentioned in the changelog).

My UPS is reporting On Battery since the update yet the front panels says 240v input / 240v output.

APC	001,029,0702	DATE	2026-05-28 20:55:51 +0100
HOSTNAME	Tower	VERSION	3.14.14 (31 May 2016) slackware
UPSNAME	Tower	CABLE	USB Cable
DRIVER	USB UPS Driver	UPSMODE	Stand Alone
STARTTIME	2026-05-28 20:53:55 +0100	MODEL	Offline UPS
STATUS	ONBATT	LOADPCT	9.0 Percent
BCHARGE	100.0 Percent	TIMELEFT	60.0 Minutes
MBATTCHG	20 Percent	MINTIMEL	10 Minutes
MAXTIME	0 Seconds	OUTPUTV	240.0 Volts
DWAKE	-1 Seconds	ALARMDEL	30 Seconds
LINEFREQ	50.3 Hz	NUMXFERS	1
XONBATT	2026-05-28 20:53:57 +0100	TONBATT	118 Seconds
CUMONBATT	118 Seconds	XOFFBATT	N/A
SELFTEST	NO	STATFLAG	0x05060010
SERIALNO	000000000	END APC	2026-05-28 20:55:55 +0100

Edited May 28May 28 by Hitcher

Updated from 7.3, no issue.

Also, I just want to take a moment to commend the Unraid team on this blitz of security updates. You guys are on a roll with all these updates recently, great to see! Bravo!

7.3 to 7.3.1 no problems.

I do have an issue that I've been chasing ever since updating to 7.3, and I cannot say unraid caused this. However, when I updated and migrated to SATA for the boot device, I DECLINED to let unraid attempt set the boot order automatically. I wanted to manage BIOS settings myself. Unfortunately, since then, I have been unable (most times) to enter the BIOS on my Supermicro X11SCZ-F. The first thing I see on screen during boot is unraid loading AFTER the unraid boot screen where you can select how unraid boots. I do not even see the Supermicro splash screen or the option to enter the BIOS (this seems to happen on SM boards sometimes for various reasons based on Google). I have tried everything including removing my Nvidia card and trying on board DP, DVI, and VGA. I also do not even get a screen on IPMI (I can't understand how this is possible, just blank)! If I press DEL during power up, I get a blank screen (monitor will shut off no signal), but I do enter the BIOS because I can press the correct keys to reset to default and save. I also get "ab" if I snoop which means that the computer is sitting there in the BIOS. But there is absolutely no display coming out of my MB on any of its ports or IPMI. I've messed with it for hours last week and accidentally got into the BIOS after resetting the BIOS (shorted the jumpers), and reinstalled my Nvidia card, and was accidentally on that input on my monitor during boot. I set everything as I need it because I knew it may be my only shot (and it was). I have not been able to get back into my BIOS again, and I certainly don't want to reset it again in case I can't get back in ever. I'm planning to start a ticket with Supermicro.

I'm surprised unraid is capable of setting the boot order on most motherboards. Is it possible unraid boinked something even though I did not allow unraid to try to automatically do it? Is there any way to unboink it?

Thanks all, I really love 7.3.x!

Edited May 28May 28 by craigr

Updated successfully from Version: 7.3.0-rc2 to Version: 7.3.1 without issues!

7 hours ago, craigr said:

Is it possible unraid boinked something even though I did not allow unraid to try to automatically do it?

Don't see how that is possible, especially if you opted out of letting Unraid change the boot order.

7.3.0 > 7.3.1 working fine here so far

I just finished upgrading six of my unraid setups (unRAID4 to unRAID9) from 7.3.0 to 7.3.1. They had no issues.

On 5/27/2026 at 9:58 PM, ezhik said:

Updated three systems from 7.2.7 to 7.3.1 - no issues. Running on USBs. I skipped the config wizard post-reboot on login.

Thanks!

I'm a little confused. I went to 7.2.7 because of some CVEs and it seemed that 7.2.7 was newer than 7.3.0.

Is 7.3.1 now the newest with all of the cumulative patches/updates for the flurry of recent CVEs?

9 minutes ago, nraygun said:

Is 7.3.1 now the newest with all of the cumulative patches/updates for the flurry of recent CVEs?

7.3.1 is the latest. But along with the new licensing system the "previous" branch i.e. currently 7.2 still gets security updates for those whose updates expired and they can't upgrade to 7.3 without extending.

Edited May 30May 30 by Kilrah