Unraid OS 7.3.3 is the latest stable release, bringing security fixes, Linux kernel 6.18.54-Unraid, Docker 29.8.2, ZFS 2.4.4, Unraid API 4.37.5-2, and improvements to File Manager and the WebGUI.

We recommend upgrading to receive the security fixes in this release. The changes below are cumulative compared with Unraid OS 7.3.2.

Security

This release hardens first-time root-password setup and privileged terminal requests, blocks unsafe API-key authorization redirects, improves UPnP remote-access discovery, and safely handles guest-agent content in VM Manager.

The cumulative 7.3.3 changelog includes these notable package security updates compared with 7.3.2:

• OpenSSL 3.5.7 → 3.5.8-2.

• Samba 4.22.10-2_LT → 4.22.11-2_LT.

• PHP 8.4.23-1_LT → 8.4.26-1_LT.

• nginx 1.30.3-1_SBo_LT → 1.30.4-1_SBo_LT.

The full 7.3.3 release notes contain the package-by-package changelog and security annotations.

Linux Kernel

The Linux kernel is updated to 6.18.54-Unraid.

Docker

Docker engine is updated from 29.5.3 to 29.8.2.

Docker Manager retains the shared default icon when a container without its own icon is removed or updated. Thanks to chodeus for this fix.

Storage / File Manager

ZFS is updated from 2.4.3 to 2.4.4. This release also fixes failures that could interrupt access to user shares or prevent file operations from completing:

• File Manager copy and move operations to exclusive user shares no longer fail with a symlink-depth error.

• The user-share filesystem, shfs, no longer deadlocks when concurrent file-lock requests exhaust its FUSE worker pool.

• An shfs assertion failure that could make /mnt/user unavailable has been fixed.

WebGUI / System

• Configure the physical power button under Settings > Power Options to shut down, reboot, or do nothing.

• Stopped-array utilization is displayed correctly, and used/free statistics remain visible for a mounted Boot Device while the array is stopped.

• Names, logs, and other WebGUI values are displayed as text rather than interpreted as HTML.

Networking / Hardware

Additional drivers and firmware support Intel, MediaTek, and Realtek wireless hardware.

Virtualization

Hyper-V kernel support covers graphics, ballooning, storage, keyboard, VMBus, utilities, and VSOCK components.

Unraid API

Updated dynamix.unraid.net to 4.37.5-2. See the Unraid API changelog.

Base Distro

This release updates the underlying system packages with security fixes and maintenance improvements. It includes 319 package updates compared with Unraid OS 7.3.2. See the full release notes for the complete package list.

Known Issues

No new release-specific known issues are listed. See the 7.3.2 release notes for previously documented issues.

Rolling Back

See the 7.3.2 release notes for rollback guidance and compatibility limitations.

Upgrading

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

Questions about your license? See the Licensing FAQ.

Release Links

• Unraid 7.3.3 Release Notes

Thank you for the efforts and this release!

1 hour ago, ironicbadger said:

An shfs assertion failure that could make /mnt/user unavailable has been fixed.

FYI, this finally fixes this very old issue: https://forums.unraid.net/bug-reports/stable-releases/683-shfs-error-results-in-lost-mntuser-r939/

It happened to multiple users if the NFS service enabled, even if no NFS shares were being exported, disabling the service was the workaround, but anyone who wants to use NFS and was running into this can now do it, and it should no longer crash shfs.

Thank you for all your hard work!

7.3.2 to 7.3.3, working fine here so far.

It may have solved an NFS/SHFS issue I had with some large files being moved around causing fuse_hidden files to stay around and not clear

How reliable is this neu Version? Can i upgrade from 7.3.1 directly?

1 hour ago, Zonediver said:

How reliable is this neu Version? Can i upgrade from 7.3.1 directly?

My method of operation for any new software to allow several days to pass before upgrading any working server with important data on it. Instant updates are for test-bed servers and the truly daring users. Just become a follower of the release thread and see if any problems are reported and determine if those issues might affect you.

UD has lost the assigned script and automount settings for my backup drive. Someone posted another problem with UD in the UD thread.

EDIT: Ah, seems something causes udev to now gives the drive's real identifier instead of the enclosure's, so that's why reassigning was necessary. Some people on Discord have had the same problem with usb drives in array/pools which is more annoying.

Edited October 12Oct 12 by Kilrah

2 hours ago, Zonediver said:

How reliable is this neu Version? Can i upgrade from 7.3.1 directly?

Stable releases are stable releases for a reason. It’s also a patch release, so it’s considered “more safe” than a minor or major release.

In saying that, there’s no saying something unavoidable may occur, sometimes “shit happens”

Release notes have:

• Fix: File Manager copy and move operations to exclusive user shares no longer fail with a symlink-depth error.

Is that at all related to this other problem?

Updated from 7.3.2 without issue.

Many thanks.

20 minutes ago, Kilrah said:

UD has lost the assigned script and automount settings for my backup drive. Someone posted another problem with UD in the UD thread.

FWIW, my UD assignments and scripts remain in tact after the upgrade.

23 minutes ago, Kilrah said:

UD has lost the assigned script and automount settings for my backup drive. Someone posted another problem with UD in the UD thread.

There's an issue with NVMe devices only, for more details see https://forums.unraid.net/topic/92462-unassigned-devices-managing-disk-drives-and-remote-shares-outside-of-the-unraid-array/page/477/#findComment-1638590

23 minutes ago, trurl said:

Is that at all related to this other problem?

Nope, it's a different issue.

Unstable after update to 7.3.3. AMD Ryzen 5 system. Uptime of months on 7.3.2. Server rebooted 4 times last 6 hours after update. Had to downgrade again

1 hour ago, paaland said:

Unstable after update to 7.3.3. AMD Ryzen 5 system. Uptime of months on 7.3.2. Server rebooted 4 times last 6 hours after update.

If you want to troubleshoot that, please enable the syslog server, then start a new thread in the general support forum and post that after a crash, together with the diagnostics.

Upgraded my backup server from 7.3.2 to 7.3.3

Looks like it created an issue with with the ZFS master output in the main tab.

One of the drive in the array is in ZFS, this is where i ship my backups from my other unraid servers.

The zfs master pool shows my backup folder as if it's not converted to dataset yet, but it is/was.

It's locked with password and when I try to unlock it, it says operation not permitted.

Never had that problem before.

thanks,

M

36 minutes ago, MartyMcfly said:

Upgraded my backup server from 7.3.2 to 7.3.3

Looks like it created an issue with with the ZFS master output in the main tab.

One of the drive in the array is in ZFS, this is where i ship my backups from my other unraid servers.

The zfs master pool shows my backup folder as if it's not converted to dataset yet, but it is/was.

It's locked with password and when I try to unlock it, it says operation not permitted.

Never had that problem before.

thanks,

M

Never mind...

This seems to be related to ZFS buddy backup plugin.
I think there is a new option with the latest version of the plugin : Immutable set to yes. If I set to "NO", i'm then able to unlock the dataset.

So, it has nothing to do with 7.3.3

All good!

thanks,

M

Two of my three servers upgraded to 7.3.3 without issue. Those two either had no additional GPU or an NVIDIA RTX 3060. The third server booted back into the OS, but only one of its three network connections appeared in the GUI, so it appeared offline. The upgrade also pulled in the newest NVIDIA driver, which doesn’t support the older GPUs in the 3rd server and broke Plex. I rolled back to 7.3.2 to fix the networking, then had to repair the NVIDIA driver by hand. I should also mention that every few versions, an OS update changes the settings under Settings > Network Settings > Interface Rules. When that happens, I have to correct them before the server has network access again.

echo "== BOARD =="; dmidecode -s baseboard-manufacturer; dmidecode -s baseboard-product-name

echo "== NICs =="; lspci | grep -i -E "ethernet|network"

echo "== GPUs =="; lspci | grep -i -E "vga|3d|display"

BOARD

ASRock

X99 Extreme4 (Released August 2014)

NICs

00:19.0 Ethernet controller: Intel Corporation Ethernet Connection (2) I218-V (rev 05)

01:00.0 Ethernet controller: QLogic Corp. cLOM8214 1/10GbE Controller (rev 54)

01:00.1 Ethernet controller: QLogic Corp. cLOM8214 1/10GbE Controller (rev 54)

GPUs

02:00.0 VGA compatible controller: NVIDIA Corporation GM206 [GeForce GTX 960] (rev a1)

03:00.0 VGA compatible controller: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] (rev a1)

Plex issue:

Plex wouldn’t start because Docker failed at container creation, before Plex ever ran. The container was configured to use the NVIDIA runtime, and the host’s NVIDIA driver wasn’t working. That was a side effect of the Unraid 7.3.2 → 7.3.3 upgrade and rollback:

1. The Nvidia Driver plugin ended up with driver 615.78.08, which is too new for my cards. The GTX 960 (Maxwell) and GTX 1060 (Pascal) are only supported through the 580 branch, so nvidia-smi couldn’t talk to either GPU.

2. When I switched to 580.173.02, the 580 package never made it to the flash drive. Only the stale 615 package was cached, so after the reboot the kernel module was 580 but the userspace tools were 615. That mismatch caused the NVRM “API mismatch” errors and kept the container runtime from working.

Plex Fix:

1. Deleted the stale 615.78.08 package folder from /boot/config/plugins/nvidia-driver/packages/.

2. Re-downloaded 580.173.02 through Settings → Nvidia Driver, and verified the .txz and .md5 files landed on the flash drive before rebooting.

3. Rebooted. nvidia-smi now reports driver 580.173.02 and lists both GPUs, and Plex starts.
   

Update to 7.3.3 from 7.3.2 went without a hitch. Keep up the good work!

🫣 "Oh nice.. there is buttton to update in UI..." ... and forever cycling a dialog "Error something went wrong" ... remote initiated reboot going on, let's see what happens next, but something went wrong.. (from 7.3.2)

-edit-

Ok after reboot that button next to version number in banner was gone, and update through tools->updateOS went smoothly. Wow.. first time see nice things about transfaring OS to NVME... it was.. fast...

But yeah.. please fix that "Something went wrong" modal dialog that refresh back forever (practically then preventing using UI ofc). that was.. well now a bit hilarious, when fury is gone..

Edited October 20Oct 20 by ByteHeaven

FYI: Critical PHP vulnerability causes many forums to go offline waiting for a patch. Both unraid services and unraid itself IMHO need addressing this problem ASAP.

Edited October 21Oct 21 by CobraPL

7 minutes ago, CobraPL said:

FYI: Critical PHP vulnerability causes many forums to go offline waiting for a patch. Both unraid services and unraid itself IMHO need addressing this problem ASAP.

If you expose the web-interface to the internet that would be wise, but do you need to do that? If not (f.i. if you use a VPN to access the web-interface) that is the first thing I'd change. I agree that patching PHP is necessary, but most of us will probably not access UnRaid (i.e. the web-interface) from the internet directly.

3 hours ago, RikStigter said:

If you expose the web-interface to the internet that would be wise, but do you need to do that? If not (f.i. if you use a VPN to access the web-interface) that is the first thing I'd change. I agree that patching PHP is necessary, but most of us will probably not access UnRaid (i.e. the web-interface) from the internet directly.

This is not relevant, an attack can also come from within the network. For example through a compromised machine. There's absolutely no excuse this has no official announcement yet from Unraid. Even worse, from what I could find it looks like php-fpm runs as root. (Yes, the web UI's task is to do management stuff, but running whole php-fpm as root for that is terrible practice.)

We're all trusting Unraid with our data, and yet it does not feel like they're taking our security seriously. (Not only this CVE, but a while ago during one of these events Unraid also took their time with responding.) Especially with the current pricing, I'm expecting better than this.

@ironicbadger Can we expect a new Unraid version with a patched PHP either today or tomorrow?

We also need the TLS certs revoked (including other relevant packages that use an independent store updated) and the VM issue dealt with (kernel update). Tailscale also needs a related update.

All three of these issues need to be dealt with ASAP.

Edited October 21Oct 21 by warpspeed