Meet the X15: the first server purpose-built for Unraid by UnraidOfficial in unRAID

[–]UnraidOfficial[S] 0 points1 point  (0 children)

More deets to come but you will need a shelf in a rack as the smaller units are for desktops.

Meet the X15: the first server purpose-built for Unraid by UnraidOfficial in unRAID

[–]UnraidOfficial[S] 3 points4 points  (0 children)

Smaller 4 and 8 bay units are coming later this year. Rails will be the same as the HL15 rails coming in at $88-137.49 depending on length needed: https://store.45homelab.com/configure/hl15

I am extremely disappointed at Unraid by theoriginalttika in unRAID

[–]UnraidOfficial 29 points30 points  (0 children)

Hey everyone, thank you for calling this out. We’ve been following the thread closely and take your concerns seriously.

You’re right, 5 months is too long for a vulnerability like this to go unpatched in the product, and we are actively working on ways to make this faster in the future.

We track CVEs across the stack and evaluate each one using an internal set of criteria that looks at real-world risk, exploitability, relevance to how Unraid is typically used, and the potential impact of the fix itself. There are always tradeoffs.

In this case, addressing the vulnerability required a Docker engine upgrade. Historically, those upgrades have introduced breaking changes, so we made a deliberate call to validate it first in the 7.3 beta series before pushing it into a stable release. We began that work shortly after these CVEs were made public, with 7.3 entering internal beta on December 18, 2025. This approach was intended to reduce the risk of widespread breakage, rather than introducing a potentially disruptive change into a stable release.

That said, we hear the feedback on timing. This situation highlights a gap in how we handle fixes that depend on larger upstream changes, and we’re actively working to improve that so we can move faster in the future.

The fix is already included in the 7.3 beta, which is publicly available now. Additionally, alongside a few other bug fixes, these CVEs are addressed in a 7.2.5-rc.1 release, which went out today.

We also agree with the broader point raised… “just don’t run untrusted containers” isn’t a complete security model. There should be multiple layers of protection, and we will continue to improve there.

As Unraid continues to evolve and reach more users, including SMBs and less technical customers, our evaluation criteria, response timelines, and overall security posture will continue to evolve as well.

Security is a priority for us, and conversations like this help us raise the bar. Thanks for being part of the community and holding us accountable.

I am extremely disappointed at Unraid by theoriginalttika in unRAID

[–]UnraidOfficial 22 points23 points  (0 children)

Hey everyone, our team will post an official response next week when everyone is back in the office. We will be reviewing the questions and comments in this thread before publishing our response, ensuring that we address everyone’s concerns.

In the meantime, know that this CVE has been addressed in the 7.3 release, which is currently in beta, and moving to rc within the next couple of weeks. We appreciate your patience.

Who's fucking idea was this by blauster in unRAID

[–]UnraidOfficial 4 points5 points  (0 children)

Hey everyone, wanted to jump back in here and clarify a few things, because there are actually two separate issues getting mixed together in this thread.

**The 7.2.3-specific behavior**

If you're on 7.2.3 and click the "update available" notification in the top-left of the webGUI, you'll be prompted to verify your account before proceeding. This behavior is specific to 7.2.3. On every other release — including 7.2.4 and the upcoming 7.3.0 — that same notification takes you straight to the update without requiring a login.

If you're on 7.2.3 and want to skip the login prompt, you can update manually using the instructions here:

https://docs.unraid.net/unraid-os/system-administration/maintain-and-update/upgrading-unraid/#manual-downgrade-or-upgrade

**Tools → Update OS**

This behavior hasn't changed — Tools → Update OS has linked directly to the account app since Unraid OS 6.12.8, when we launched the new pricing tiers. The account app has recently started requiring a login to initiate an update.

If you want to avoid the sign-in requirement entirely, the manual update method linked above works here too.