TrueNAS SCALE CVE-2026-123033: Update to 25.10.8 Now

Last updated: November 15, 2026

Short answer: TrueNAS SCALE 25.10.8, released November 5, 2026, fixes a CVSS 8.3 authentication bypass (CVE-2026-123033) that lets an attacker on your own network take root access without a password, even on single-node installs. If your version is below 25.10.8, update now: save your system config first, then update from System Settings, reboot, and confirm 25.10.8.

TrueNAS SCALE CVE-2026-123033 — update to 25.10.8 to fix the authentication bypass that gives root access from your own network

Contents

On November 5, 2026, Rapid7 disclosed CVE-2026-123033, an authentication bypass in TrueNAS SCALE that hands an attacker on your own network full administrator access without a password, and from there, command execution as root. The flaw sits in the middleware that runs every TrueNAS SCALE system, and it affects single-node Community Edition installs just as much as enterprise high-availability pairs. The fix is a single update: TrueNAS SCALE 25.10.8, released the same day. This guide explains what the flaw is, how serious it really is, how to check whether your NAS is affected, and the exact steps to update.

What is CVE-2026-123033?

TrueNAS SCALE is run by a management service called middlewared. Between the two controllers of a high-availability (HA) appliance, middlewared uses a peer-authentication hook over the private heartbeat link, so the two controllers can trust each other. On affected versions, that hook made its trust decision from only two properties of the incoming connection: the TCP peer address and the source port. If the peer address was one of the hardcoded HA heartbeat addresses (169.254.10.1 or 169.254.10.2) and the source port was 1024 or lower, the connection was granted an internal node credential that counts as a full administrator for every API method. Administrative API access can then be used to run commands on the underlying operating system as root.

The dangerous part is how widely the hook was registered. It was present on every installation, whether or not the system is licensed for HA, has HA hardware, or has any HA configuration at all. That means single-node Community Edition systems with no HA set up are in scope, not only HA pairs. TrueNAS CORE does not share this middleware code and is not affected. The flaw was reported by spnctf through coordinated disclosure, and iXsystems rates it High, CVSS 3.1 8.3 (AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H), under CWE-290 (Authentication Bypass by Spoofing) and CWE-306 (Missing Authentication for Critical Function).

How bad is it really?

Serious, but not the way some headlines frame it. iXsystems rates the flaw High at CVSS 8.3, not critical, and the rating comes with a clear limit: exploitation is not possible from an arbitrary internet location. A stock TrueNAS system disables IPv4 link-local autoconfiguration and holds no route to the 169.254.0.0/16 range, so an attacker must be on the same layer-2 network segment as the appliance's management interface (for example a virtual machine on the same hypervisor switch, a host on the same flat VLAN, or the network gateway), and must additionally alter the return path, either by modifying routing on the TrueNAS system or by controlling the gateway. That raises the attack complexity materially.

Where those conditions are met, the impact is high. The unauthenticated access bypasses the management-interface IP allowlist and API rate limiting, can read configuration secrets, is not recorded in the audit log, and can lead to command execution as root. On a typical deployment, a TrueNAS appliance whose management interface sits on a trusted, switched management network the operator controls, the practical exposure is limited by exactly those adjacency and return-path requirements. As of November 15, 2026, no public proof-of-concept exploit has been confirmed, the flaw is not listed in CISA's Known Exploited Vulnerabilities catalog, and no exploitation has been reported. That is reassuring, but it is not a reason to wait: the fix is a routine update, and this is the second critical NAS flaw to hit home labs in a month — the KSMBD flaw in Samba showed the same pattern, a network service on your NAS turning into a way in.

Am I affected? How to check your version

Open the TrueNAS web UI and look at the Dashboard. The System Information card shows your installed version. If it reads anything below 25.10.8 on the 25.10 train, you are affected and should update. If it already reads 25.10.8 or later, the fix is in place. If you run an older train, update to the fixed release for your train. TrueNAS CORE systems are not affected at all.

Do not assume you are safe because you never set up high availability. The vulnerable hook is registered on every TrueNAS SCALE install, including a single-node Community Edition box with no HA configuration. If your NAS runs TrueNAS SCALE below 25.10.8, it is in scope, full stop.

How to update to TrueNAS SCALE 25.10.8

Update during scheduled maintenance, when no clients are connected and no disk activity is running, because the system restarts after the update. The steps below follow the official TrueNAS update procedure.

  1. Open System Settings, then Update, and check for updates. Log in to the TrueNAS web UI, open System Settings, then Update. If 25.10.8 is available on your train, it appears as a pending update.
  2. Click Apply Pending Update. If an update is available, click Apply Pending Update to install it.
  3. Save your configuration with the password secret seed. When the save prompt appears, tick Export Password Secret Seed and click Save Configuration. Keep the downloaded file somewhere safe, because it restores your system configuration if anything goes wrong with the update.
  4. Confirm and start the update. Click Confirm, then Continue to start the automatic installation. TrueNAS downloads the update file and installs it.
  5. Wait for the restart, then clear your browser cache. The system restarts after the update. Wait for it to come back up, then press Ctrl+F5 to clear the browser cache before logging in.
  6. Confirm version 25.10.8 and test your services. On the Dashboard, confirm the version reads 25.10.8. Check that your pools, shares, and apps are all working before you call it done.

If no update appears on the Update screen, check that your system is on the 25.10 train and that it can reach the update servers. If the update fails, the saved configuration file from step 3 is what lets you restore your settings, so do not skip it.

What else changed in 25.10.8?

TrueNAS SCALE 25.10.8 (Goldeye) shipped on November 5, 2026, and the CVE fix is only part of it. The release updates the Linux kernel to 6.12.113, fixing more than 1,600 upstream CVEs, several of them critical or high severity in components TrueNAS uses. It also fixes a dataset passphrase exposure in internal job arguments (NAS-144783), where a passphrase-encrypted dataset unlocked from the web interface had its passphrase stored unredacted in job details, plus NVMe over TCP I/O errors on large transfers and fixes for SMB, rsync, Cloud Sync, TrueNAS Connect, and Apps issues.

One honest note on sourcing: the release announcement itself does not name CVE-2026-123033. The CVE fix in 25.10.8 is confirmed in the iXsystems security advisory, not in the announcement, which is why this guide cites the advisory as the primary source for the flaw. Early reports in the release thread are mostly smooth updates, though one user reported the Garage app breaking inbound connections after updating, fixed by stopping the app from the console. That is a reminder to test your apps after the reboot in step 6, not a reason to skip the update.

What if you cannot update right now?

If you cannot update today, apply the vendor's recommended mitigation now: keep the TrueNAS management interface on a dedicated, trusted management network, and make sure no untrusted host shares the management interface's layer-2 segment. Isolate your hypervisor virtual switches and management VLANs so that no untrusted party can send traffic from a 169.254.10.x source address toward the management interface. According to the vendor, this fully blocks the exposure, and it is the recommended action today for systems that cannot be updated yet.

The same thinking applies to the rest of your home network. A NAS that holds every family photo and backup deserves the same isolation as any other critical service, and root access on a NAS is the starting point for ransomware, which is exactly how the SafePay ransomware factory-resets a NAS. If your management interface shares a flat network with guest devices, IoT gadgets, or a virtual machine you do not fully trust, that is the gap to close first, even before the update finishes. For the wider network, our Pi-hole guide covers keeping the home network tidy and under your control.

Frequently asked questions

Is my single-node TrueNAS affected, or only HA pairs?

Your single-node system is affected. The vulnerable hook is registered on every TrueNAS SCALE install, including single-node Community Edition systems with no HA set up. Only TrueNAS CORE is not affected.

Can someone attack my TrueNAS from the internet with this flaw?

No. The attacker must be on the same layer-2 segment as the management interface and must also alter the return path. It is not exploitable from an arbitrary internet location.

Which TrueNAS versions are affected?

TrueNAS SCALE versions before 25.10.8 on the 25.10 train are affected. The fix is in 25.10.8 and later. If you are on an older train, update to the fixed release for your train. TrueNAS CORE is not affected.

How do I check my TrueNAS version?

Open the web UI and look at the Dashboard. The System Information card shows the installed version. If it is below 25.10.8, update.

Is there a public exploit for CVE-2026-123033?

As of November 15, 2026, no public proof-of-concept exploit has been confirmed, and the flaw is not listed in CISA's Known Exploited Vulnerabilities catalog. No exploitation has been reported. The fix is a routine update, so there is no reason to wait for an exploit to appear.

What should I do before updating to 25.10.8?

Save your system configuration with Export Password Secret Seed, and update during scheduled maintenance because the system restarts. After the update, confirm the version reads 25.10.8 and test your pools, shares, and apps.

Sources

About the author: Bilal Riaz is the founder of The Homelab Fixer, writing step-by-step guides for NAS, Docker, and self-hosting.

Source: iXsystems TrueNAS security advisory and NVD, November 5, 2026; TrueNAS 25.10.8 release announcement. All version numbers and CVSS scores in this guide were checked against the vendor advisory on November 15, 2026.

Comments

Popular posts from this blog

Nginx 502 Bad Gateway in Docker? 4 Fixes That Actually Work (2026)

GitLab Update: Patch the CVSS-10 RCE Tonight — Self-Hosted Fix Guide (CVE-2026-110264)

Pi-hole v6.5 Update: 6 Breaking Changes and How to Fix Them