Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Unraid OS 7.3.4 Now Available

Featured Replies

Unraid OS 7.3.4 is now available. This release includes WebGUI security fixes, updates the Linux kernel to 6.18.58, and fixes Docker icon handling and File Manager operations.

It also includes PHP 8.4.27, which patches CVE-2026-109618 and CVE-2026-109619, a pair of critical (CVSS 9.2) unauthenticated remote code execution vulnerabilities in PHP.

All users are encouraged to update.

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

Highlights

Security

  • PHP 8.4.27 patches CVE-2026-109618 and CVE-2026-109619, critical (CVSS 9.2) unauthenticated remote code execution vulnerabilities

  • WebGUI security fixes

  • Updated packages with CVE remediations, including curl (21 CVEs), OpenSSL (13 CVEs), xorg-server (11 CVEs), libXi (8 CVEs), libX11, libXtst, libXpm, libXrender, libpng, and nginx; openssh and libarchive also receive security fixes

Linux Kernel

  • Update to 6.18.58-Unraid

Containers / Docker

  • Fix: Docker icon handling

Storage

  • Fix: File Manager operations

Base Distro

  • 44 packages updated

Links

I've just upgraded my NAS from 7.3.2.

After rebooting one of my Docker stacks managed by Compose Manager Plus was broken because the ID of the network "br0" had changed. Not sure if normal or not.

Compose down + compose up fixed the problem.

Not sure if related but I've lost control over one of my PWM fans...

EDIT: Probably nothing to do with that update, seems to be hardware related.

Edited by googleg

41 minutes ago, googleg said:

After rebooting one of my Docker stacks managed by Compose Manager Plus was broken because the ID of the network "br0" had changed. Not sure if normal or not.

Is it new for you to have stacks on br0? It's been that way for ages for me, br0 is created fresh each boot so has a new id, need to make your own macvlan/ipvlan network to avoid that

Edited by Kilrah

No it is not new and it's the first time I have that issue.

Coming from 7.3.3.

No issues so far.

VM (Win 11 with gpu also and pci-e usb card passthrough) working well.

My server had updated from 7.3.2 to 7.3.3 recently, just the reboot was still pending.

I didn't do it, I rebooted the server first to finish the first reboot before doing the second.

But should it have worked to immediately do the second update and reboot then?

Just wondering.

Same here. No issues upgrading from 7.3.3 to 7.3.4.

1 HA VM and about 30 Docker containers—no issues

Thanks for the quick fix for the recent PHP issues.

-faxxe

Any plans for a 7.2.9 release to get these security updates for those who can't update?

7 minutes ago, DataBitz said:

Any plans for a 7.2.9 release to get these security updates for those who can't update?

Currently they are saying no as they seem to think 7.4, although not yet being stable is a valid release so 7.3 is the previous branch. I think this is honestly wrong.

23 minutes ago, DataBitz said:

Any plans for a 7.2.9 release to get these security updates for those who can't update?

+1 to @DataBitz. I’m on a Starter license whose updates lapsed last year, still on 7.1.3, and I’d really like to see a free security-only patch for this one. A CVSS 9.2 unauthenticated RCE in the WebGUI feels like it should be fixed for everyone, not only for licenses that are current. Happy to pay for new features. Security fixes for critical holes feel different. Thanks for turning 7.3.4 around so fast.

Upgaded from 7.2.2 to 7.3.4 no issues so far. Thanks for the fast response to CVE-2026-109618 and CVE-2026-109619, a pair of critical (CVSS 9.2) unauthenticated remote code execution vulnerabilities in PHP.

Update from 7.3.1 with no issues - thanks for the good work 👍

5 hours ago, Flubster said:

Currently they are saying no as they seem to think 7.4, although not yet being stable is a valid release so 7.3 is the previous branch. I think this is honestly wrong.

The FAQ for the licence says the last 2 releases get updates. It says that once a release has reached beta status it counts. In practice that means most of the time this will be the last stable release and the one currently being worked on.

3 hours ago, itimpi said:

The FAQ for the licence says the last 2 releases get updates. It says that once a release has reached beta status it counts. In practice that means most of the time this will be the last stable release and the one currently being worked on.

well considering the installer and licence managers are still suggesting 7.2 is a valid current supported release I suggest someone aligns all the tools, because counting a RC (which is NOT stable) as a release is sketchy.

5 hours ago, Flubster said:

well considering the installer and licence managers are still suggesting 7.2 is a valid current supported release I suggest someone aligns all the tools, because counting a RC (which is NOT stable) as a release is sketchy.

I have heard that 7.2.9 will be coming, but not sure when... in the meantime, this can address 7.2 (requires 7.2.8):

https://github.com/dkaser/unraid-unofficial-update

Updated from Unraid 7.3.1 to 7.3.4.

Before the upgrade I made a full backup (appdata + flash/config) and disabled Docker and VM Manager in Unraid settings. After the update and reboot, everything came back up normally. Docker and VMs were re-enabled afterwards and all services are working fine.

I also run custom low-level power-tuning scripts on this server (PCIe ASPM/runtime PM tweaks, SATA link power management, NVMe autosuspend, Coral TPU link tuning, powertop auto-tuning, and CPU governor/EPP settings), so I’ll keep an eye on idle power draw for a while to make sure it stays the same.

So far, so good - no issues

upgraded without issues. thanks for posting the php security fix.

Updated frrom Unraid 7.3.3 to 7.3.4 on my Ugreen DXP4800 Pro.

Where with Unraid 7.3.3 and earlier, I could shutdown the NAS by pushing the power button, with Unraid 7.3.4 this no longer works. Shutdown via UI is still possible.

Edited by UNRAIDyNAS

7 hours ago, UNRAIDyNAS said:

Updated frrom Unraid 7.3.3 to 7.3.4 on my Ugreen DXP4800 Pro.

Where with Unraid 7.3.3 and earlier, I could shutdown the NAS by pushing the power button, with Unraid 7.3.4 this no longer works. Shutdown via UI is still possible.

Look here: Settings >>> System Settings >>> Power Options >>> Power Button

image.png

39 minutes ago, Frank1940 said:

Look here: Settings >>> System Settings >>> Power Options >>> Power Button

image.png

I have this setting enabled and am still having the same issue.
Seems to be a ACPI bug in the kernel version that unraid is currently using. The kernel creates the ACPI device node /sys/bus/acpi/devices/LNXPWRBN:00, but never registers the corresponding /sys/bus/platform/devices/LNXPWRBN:00 platform device. fixed in https://github.com/torvalds/linux/commit/ab06eb920401
At least that is the conclusion I came to after a night of trying to diagnose it.

Thanks for your replies.

I also have the Power Button correctly configured, so that is not the cause of the issue.

Upgraded from 7.3.2 without issues

Eli stole the header fade once again.

Upgraded to 7.3.4 from 7.3.3, server starts but I can't access webgui anymore, and logs are filled up with:
Oct 26 17:05:53 Odin webgui: curl error: Failed to connect to localhost:80 over unix:///var/run/nginx.socket after 0 ms: Could not connect to server endpoint: diagnostics

Oct 26 17:05:53 Odin publish: curl to diagnostics failed

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.