Unraid 7.2.5 is out today and is a recommended update for all users. This is a security and bugfix release.

What's in this release:

• 3 WebGUI security fixes — required a logged-in session to exploit.

• Linux kernel 6.12.85-Unraid — patches CVE-2026-31431 (Copy Fail local privilege escalation) and CVE-2026-31430 (X.509 out-of-bounds access)

• Docker updated to 29.3.1 — includes runc fixes for CVE-2025-31133, CVE-2025-52565, and CVE-2025-52881

• Fixed MAC Address field in Docker templates — addresses the MAC address churn introduced by Docker Engine 28; set a fixed value if your containers rely on a stable MAC for DHCP reservations, firewall rules, or monitoring

• Storage fixes — mover empty-disk action restored on systems with no pool assigned; non-standard partition layouts preserved on unassign/reassign

• Login page — custom case-model images restored (regression from 7.2.4)

• Unraid API — fixes a startup bootstrap timeout/restart loop and improves license state refresh

• Multiple CVEs patched across curl, OpenSSL, GnuTLS, libpng, xorg-server, libpcap, libtasn1, libXpm, p11-kit, PHP, xz, and more

Breaking change: Docker containers may receive a new dynamically generated MAC address each time they are created - this is due to a change in Docker Engine 28. If a container needs a stable network identity for DHCP reservations, router or firewall rules, switch ACLs, monitoring, or similar workflows, set a fixed value in the new MAC Address field on the Docker template. This follows Docker Engine 28+ behavior for bridge and macvlan network endpoints; see the Docker Engine 28 release notes.

---

Full Release Notes

---

Blog Post

For step-by-step upgrade instructions, see Updating Unraid in the docs.

Got Bugs? Please report them here!

Updated 7.2.4 ---> 7.2.5 Successfully with no issues. Thank you for your hard work, I appreciate all of you!

😔 Updated 7.2.4 ---> 7.2.5 and now all of my gpu dependant containers stopped working. nVidia plug-in update incomming ?

nvidia-container-cli: ldcache error: process /sbin/ldconfig failed with error code: 1

Great work getting this out so fast and including CVE-2026-31431

Up and running fine here so far from rc2.

Edited May 1May 1 by warpspeed

37 minutes ago, yanno said:

😔 Updated 7.2.4 ---> 7.2.5 and now all of my gpu dependant containers stopped working. nVidia plug-in update incomming ?

nvidia-container-cli: ldcache error: process /sbin/ldconfig failed with error code: 1

Having the same issue

1 hour ago, yanno said:

😔 Updated 7.2.4 ---> 7.2.5 and now all of my gpu dependant containers stopped working. nVidia plug-in update incomming ?

nvidia-container-cli: ldcache error: process /sbin/ldconfig failed with error code: 1

Same here, the data in /etc/docker/daemon.json needs update for docker engine29

temporary fix:
nvidia-ctk cdi generate --output=/etc/cdi/nvidia.yaml
nvidia-ctk runtime configure --runtime=docker --cdi.enabled
disable and re-enable docker

also experiencing this issue after 7.2.4 -> 7.2.5 upgrade. jellyfin doesn't start and i get "Execution error Server error".

if that is a temporary fix, what do we need to do once the real fix has been implemented?

Edited May 1May 1 by Dr_Noonia_Soong

Thanks for letting us know about this NVIDIA issue - we’ll take a look and see what we can do to resolve this as it will also affect users on 7.3. I’ll check into this tomorrow and update this thread. If there isn’t a bug report already, please make one here as well: https://product.unraid.net

7.2.4->7.2.5:

The three Docker containers essential for Nextcloud—which I built and ran using the docker-compose plugin—stopped starting.

Despite multiple attempts to rebuild them, it seems that some old IDs in the Docker database were the cause of the problem.

I then deleted all 34 Docker containers and reinstalled them. Now they’re all running again.

Unraid 7.2.4 with Docker compose plugin - Immich fails to start with error -
Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error running prestart hook #0: exit status 1, stdout: , stderr: Auto-detected mode as 'legacy'

nvidia-container-cli: ldcache error: process /sbin/ldconfig failed with error code: 1

4 hours ago, MedBox said:

Same here, the data in /etc/docker/daemon.json needs update for docker engine29

temporary fix:
nvidia-ctk cdi generate --output=/etc/cdi/nvidia.yaml
nvidia-ctk runtime configure --runtime=docker --cdi.enabled
disable and re-enable docker

2 minutes ago, Unraid-arr said:

Unraid 7.2.4 with Docker compose plugin - Immich fails to start with error -
Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error running prestart hook #0: exit status 1, stdout: , stderr: Auto-detected mode as 'legacy'

nvidia-container-cli: ldcache error: process /sbin/ldconfig failed with error code: 1

Thanks, this helped me with my issue. Can you please let me know if this will persist across reboots?

You saved my brain from a kernel panic at 2AM after updating UnRaid.

All the containers with Extra Parameters: --net=container:<container-name> failed to start, and I had to remove those Extra Parameters and manually set the container networks from none in dropdown to the container name. Just curious, why remove the parameter option?

Edited May 1May 1 by Unraid-arr

5 hours ago, MedBox said:

Same here, the data in /etc/docker/daemon.json needs update for docker engine29

temporary fix:
nvidia-ctk cdi generate --output=/etc/cdi/nvidia.yaml
nvidia-ctk runtime configure --runtime=docker --cdi.enabled
disable and re-enable docker

Thanks for the fix 👍

Please update to version 2026.05.01 of the nvidia plugin for the CDI update.

For more info see this thread. https://forums.unraid.net/topic/98978-plugin-nvidia-driver/page/232/#findComment-1620557

With this update automatic loading Keyfile from FTP Server via go file stopped working..
With 7.2.4 worked perfectly.

Go File (inserted in Line 20...):

_{# Keyfile}

_{wget --user=abcd--password='password' ftp://server/keyfile.7z -O /root/keyfile.7z}

_{7z x -p'OtherPwd' /root/keyfile.7z -o/root/}

_{rm /root/keyfile.7z}

_{# Start the Management Utility}

_{/usr/local/sbin/emhttp}

_{# Remove Keyfile from Server}

_{sleep 20}

_{rm /root/keyfile}

Trying manually via shell wget and 7z working...

Upgraded "main" unRAID Server from 7.2.4 to 7.2.5 - no issues so far (only have Intel CPU/GPU for transcoding).

Thanks to all of the unRAID Team!

Had to downgrade as all my compose stacks broke...

EDIT: Looked into it, using docker container ls -a it looks like something 2 years ago left some container folders in the Docker filesystem for containers that had been removed, previous Docker version didn't care or even see them but apparently Docker 29 does and for some reason wants to reuse the same hashes, then fails to create containers since there's already a folder. Removed the related folders, restarted Docker and everything's good again.

Edited May 30May 30 by Kilrah

7 hours ago, SimonF said:

Please update to version 2026.05.01 of the nvidia plugin for the CDI update.

For more info see this thread. https://forums.unraid.net/topic/98978-plugin-nvidia-driver/page/232/#findComment-1620557

this has resolved the issue, thank you!!

Any idea why my Sabnzbd container would fail after this update (7.2.5)? The container starts but web service is unavailable and other dockers can't see it. No changes to config.

unraidpvr-diagnostics-20260501-1701.zip

Edited May 1May 1 by Rick Gillyon

This release is recommended for all 7.2.x users.

So I assume this means that all of these fixes are included in the 7.3 beta 2 rc-1?

Edited May 1May 1 by strike

--runtime=nvidia in place of --gpus=all is the fix for the docker issue I believe.

Intel boot loader reports 'Boot failure' after 7.2.4 --> 7.2.5 upgrade.

Has worked flawlessly since back in the 6.8 days. Does not boot so am unable to

generate diagnostics.

-- Tom

Copying /config from the backup to the USB did not work, still Boot Error.

Copying all files in the root of the backup (e.g. linuz boot files plus all others) did not work Boot Error.

Used USB Creator 1.1.0 on a Win10 machine to recreate the USB from the backup file, and that successfully booted into

the older version (7.2.3 was the last backup). UEFI server boot.

-- Tom

2 hours ago, Tom3 said:

Used USB Creator 1.1.0 on a Win10 machine

Does it boot if you use that to create a 7.2.5 stock install? See if it boots stock, before restoring any of the backup files.

Since upgrading to 7.2.5 my nextcloud instance isn't accessable, via local ip or via cloudflare, can't figure out why. Also my server has gone from ~10% idle to 70% idle usage with php-fpm: pool www being the culprit.

Any ideas? Will have to downgrade if I can't figure it out today.