CVE-2026-107347

HashiCorp Nomad and Nomad Enterprise are vulnerable to symlink following during same-client allocation data migration. A malicious workload may change permissions and ownership of host directories.

HashiCorp Nomad and Nomad Enterprise are vulnerable to cross-namespace authorization bypasses in several read-only API endpoints. An authenticated user with read permissions in one namespace may view information about objects in other namespaces. This is fixed in Nomad Community Edition 2.1.1 and Nomad Enterprise 2.1.0, 1.11.12, and 1.10.18.

A vulnerability in Nomad and Nomad Enterprise allows cross-namespace authorization bypass in the dynamic host volumes feature. An operator with host volume delete permission in one namespace can delete a sticky volume claim belonging to a job in another namespace.

HashiCorp Nomad and Nomad Enterprise are vulnerable to a sandbox escape in the Docker task driver that allows a job submitter to bind-mount a host path into a container even when volume bind mounts are disabled, potentially leading to reading and writing files on the host.

The vulnerability in Nomad and Nomad Enterprise is due to the lack of enforcement of the allow_privileged restriction for the Docker task driver's host namespace mode options. This allows an authenticated job submitter to run a container in a host namespace and access information belonging to the host or other workloads on the same client.

HashiCorp Nomad's exec2 task driver prior to 0.1.2 is vulnerable to arbitrary file read and write on the client host as the Nomad process user via a symlink attack. The vulnerability is fixed in version 0.1.2 of the exec2 task driver.

HashiCorp Nomad and Nomad Enterprise prior to 2.0.1 are vulnerable to arbitrary file read and write on the client host as the Nomad process user through a symlink attack.