Live › vulnerability › CVE-2026-119168
Nomad can follow a symlink during allocation data migration on the same client, so a malicious workload can change the permissions and ownership of host directories. An attacker can use this to reach or modify host files and possibly escalate privileges.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-29 19:26 UTC. All times on this page are UTC.
Teams running Nomad or Nomad Enterprise clients where workloads share a host and allocation data migration runs between clients. Clusters on a fixed release line or without multi-workload client hosts are less exposed. The sources do not state which default configurations trigger the migration path.
No product ranges from the sources yet.
nomad version2.1.02.1.0, 1.11.12, 1.10.18Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
HashiCorp Nomad and Nomad Enterprise are vulnerable to symlink following during same-client allocation data migration that may allow a malicious workload to change permissions and ownership of host directories. This could allow unauthorized access to host data or modification of host files, potentially leading to privilege escalation. This vulnerability (CVE-2026-119168) is fixed in Nomad 2.1.0 and Nomad Enterprise 2.1.0, 1.11.12, and 1.10.18.
This page as .md · .json · in your agent: get_signal("CVE-2026-119168")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.