CVE-2026-14891: 
Nomad vulnerability analysis and mitigation

CVE-2026-14891 is a sandbox escape vulnerability in the Docker task driver of HashiCorp Nomad and Nomad Enterprise that allows an authenticated job submitter to bind-mount host paths into containers even when volume bind mounts are explicitly disabled, potentially enabling unauthorized reading and writing of files on the host system. The vulnerability affects Nomad and Nomad Enterprise from version 0.4.1 up to (but not including) 2.0.4, and was publicly disclosed on July 8, 2026. It carries a CVSS v3.1 base score of 8.7 (High) (GitHub Advisory, HashiCorp Forum).

The root cause is classified as CWE-59 (Improper Link Resolution Before File Access / 'Link Following'), where Nomad's Docker task driver fails to properly validate or restrict volume mount configurations submitted in job definitions, allowing a symlink or path traversal technique to bypass the volume bind mounts disabled policy. An attacker with job submission privileges can craft a malicious job specification that references host filesystem paths, causing the Docker task driver to mount those paths into the container without proper enforcement of the configured restrictions. The attack vector is network-based, requires high privileges (job submission access), low complexity, and no user interaction, but results in a scope change affecting the host system beyond the container boundary (GitHub Advisory, HashiCorp Forum).

Successful exploitation allows an authenticated job submitter to escape the container sandbox and gain read and write access to arbitrary files on the underlying host system. This can lead to exposure of sensitive host data (credentials, configuration files, secrets), modification or destruction of host files, and potential for privilege escalation or lateral movement if sensitive files such as SSH keys or cloud credentials are accessed. Availability is not directly impacted, but the high confidentiality and integrity impacts make this a significant risk in multi-tenant or shared Nomad cluster environments (GitHub Advisory, HashiCorp Forum).

As of the disclosure date, there is no public proof-of-concept exploit and no evidence of in-the-wild exploitation (GitHub Advisory). The EPSS score is approximately 0.316% (24th percentile), indicating a low near-term exploitation probability. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. Exploitation requires authenticated access with job submission privileges, which limits the attack surface compared to unauthenticated vulnerabilities, though insider threats or compromised accounts remain a concern.

1. Reconnaissance: Identify a target HashiCorp Nomad or Nomad Enterprise cluster running a vulnerable version (0.4.1 up to < 2.0.4) with the Docker task driver enabled and volume bind mounts configured as disabled.
2. Obtain job submission credentials: Acquire valid credentials or an ACL token with job submission privileges (e.g., through credential theft, insider access, or a compromised CI/CD pipeline).
3. Craft malicious job specification: Create a Nomad job definition (HCL or JSON) that specifies a Docker task with a volume or mount stanza referencing a sensitive host path (e.g., /etc, /root, /var/run/docker.sock) using a path or symlink that bypasses the bind-mount restriction check.
4. Submit the job: Use the Nomad CLI (nomad job run malicious.hcl) or API to submit the crafted job to the cluster.
5. Access host files: Once the container starts with the host path mounted, execute commands within the container to read or write sensitive host files, such as extracting credentials, SSH keys, or modifying system configurations to enable persistence or lateral movement (GitHub Advisory, HashiCorp Forum).

• Logs: Nomad agent logs showing Docker task driver mounting host paths that should be restricted by policy; audit log entries for job submissions containing unusual volume or mount stanzas referencing host filesystem paths.
• File System: Unexpected access or modification timestamps on sensitive host files (e.g., /etc/passwd, /root/.ssh/authorized_keys, /var/run/docker.sock) coinciding with container workload activity.
• Network: Outbound connections from Nomad client nodes to unexpected external IPs following job submission events, potentially indicating data exfiltration.
• Process: Docker containers running with bind mounts to host paths that are not authorized by cluster policy; docker inspect output showing unexpected Binds entries for running containers associated with Nomad-managed tasks.

HashiCorp has released patches addressing this vulnerability: Nomad Community Edition 2.0.4, Nomad Enterprise 2.0.4, Nomad Enterprise 1.11.8, and Nomad Enterprise 1.10.14. Organizations should upgrade to one of these versions as the primary remediation. As an interim workaround, restrict job submission privileges to only highly trusted users and audit existing ACL token assignments; additionally, monitor job submissions for suspicious volume mount configurations. Review and tighten Nomad ACL policies to limit the blast radius of any compromised job-submitter accounts (HashiCorp Forum, GitHub Advisory).

HashiCorp disclosed the vulnerability through their official security advisory forum (HCSEC-2026-21) on July 8, 2026, simultaneously releasing patched versions. The vulnerability was also referenced in a CISA weekly bulletin (SB26-194), indicating it received attention from the broader security community. No notable independent researcher commentary or significant social media discussion has been identified beyond standard vulnerability aggregator coverage.