CVE-2026-123033: High severity vulnerability
Authentication bypass in the HA heartbeat origin check in middlewared in TrueNAS SCALE before 25.10.8 (and in release trains before their respective fixes) allows an attacker on the same network segment to achieve unauthenticated full-administrator API access and execute commands as root. middlewared registers the HA peer-authentication hook (hapermission) unconditionally, with no failover-licence or heartbeat-interface check. An unauthenticated connection whose TCP peer address is a hardcoded HA heartbeat address (169.254.10.1 or 169.254.10.2) and whose peer port is <= 1024 is granted a node credential that is authorized for every API method and treated as full administrator. Both conditions are properties of the attacker's own socket, and thus an attacker on the same layer-2 segment satisfies them without forging anything. The hook is present on non-HA, unlicensed, single-node Community Edition installations. The fix additionally requires that the connection terminate on the HA heartbeat listener (a local address/port the attacker cannot control).
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
TrueNAS SCALEto a version that resolves this vulnerability.Fixed in 25.10.8
Event History
Frequently Asked Questions
Which deployments are exposed?
The affected hook is present even on non-HA, unlicensed, single-node Community Edition installations. An attacker must be on the same layer-2 network segment as the target.
What does an attacker need to exploit this?
No authentication, credentials, or user interaction are required. The attacker needs to establish a connection with a TCP peer address of 169.254.10.1 or 169.254.10.2 and a source port of 1024 or lower; these are controlled by the attacker’s own socket.
What access does successful exploitation provide?
Successful exploitation grants unauthenticated full-administrator API access. The attacker can invoke every API method and execute commands as root.
Which versions contain the fix?
The issue is fixed in TrueNAS SCALE 25.10.8 and in the corresponding fixes for other release trains. The provided information does not identify the fixed version for each earlier release train.