CVE-2026-14373: 
Nomad vulnerability analysis and mitigation

CVE-2026-14373 is an authorization bypass vulnerability in HashiCorp Nomad and Nomad Enterprise affecting the Docker task driver's host namespace mode options. The flaw stems from the failure to enforce the allow_privileged restriction, allowing authenticated job submitters to run containers in host namespace mode and access host or co-tenant workload information. Affected versions span from 0.4.1 up to (but not including) 2.0.4 for both Nomad Community Edition and Nomad Enterprise. It was published on July 8, 2026, with a CVSS v3.1 base score of 7.7 (High) (GitHub Advisory, HashiCorp Advisory).

The root cause is CWE-862 (Missing Authorization): Nomad's Docker task driver does not properly check the allow_privileged configuration setting when a job specifies host namespace mode options (e.g., pid_mode, ipc_mode, network_mode set to host). This means the intended operator-level restriction that prevents unprivileged job submitters from accessing host namespaces is silently bypassed. An attacker with low-privilege network access and job submission rights can craft a Nomad job specification that sets host namespace options, causing the container to share the host's PID, IPC, or network namespace without triggering the expected authorization check (GitHub Advisory, HashiCorp Advisory).

A successful exploit allows an authenticated but otherwise low-privileged job submitter to run a Docker container sharing the host's namespaces, exposing host-level process information, inter-process communication, and network state. This creates a significant confidentiality risk: the attacker can observe sensitive data from the host OS and from other workloads co-located on the same Nomad client node. Integrity and availability are not directly impacted, but the information disclosure could facilitate lateral movement to other workloads or privilege escalation on the host (GitHub Advisory, HashiCorp Advisory).

No public proof-of-concept exploit code has been identified, and there is no evidence of in-the-wild exploitation at this time. The EPSS score is approximately 0.248% (16th percentile), indicating a low near-term exploitation probability. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, and NVD SSVC assessment classifies exploitation as "none" and automation as "no" (GitHub Advisory, HashiCorp Advisory).

1. Reconnaissance: Identify a Nomad cluster running a vulnerable version (0.4.1 through 2.0.3) with the Docker task driver enabled and the allow_privileged restriction configured to block privileged containers.
2. Obtain job submission credentials: Acquire an authenticated Nomad token or ACL credential with job submission permissions (e.g., a developer or CI/CD service account).
3. Craft a malicious job specification: Write a Nomad job HCL/JSON file that uses the Docker task driver and sets host namespace options such as pid_mode = "host", ipc_mode = "host", or network_mode = "host" within the config block.
4. Submit the job: Use the Nomad CLI (nomad job run malicious.nomad) or API to submit the crafted job to the cluster. The allow_privileged check is not enforced, so the job is accepted and scheduled.
5. Access host namespace data: Once the container starts in host namespace mode, execute commands within the container (e.g., ps aux, ss -tulnp, cat /proc/<pid>/environ) to enumerate host processes, network connections, environment variables, and data from co-tenant workloads (HashiCorp Advisory, GitHub Advisory).

• Logs: Nomad audit logs showing job submissions by low-privilege tokens that include Docker task driver configurations with pid_mode, ipc_mode, or network_mode set to "host"; Nomad client logs showing containers launched with host namespace flags despite allow_privileged = false policy.
• Process: Unexpected container processes visible in the host PID namespace (e.g., Docker containers appearing in ps aux output alongside host processes); container processes accessing /proc/<host_pid>/ paths.
• Network: Containers sharing the host network namespace generating traffic that appears to originate from the host IP rather than a container-specific IP; unexpected outbound connections from the Nomad client node.
• File System: Evidence of container processes reading sensitive host files accessible via shared namespaces (e.g., /proc/net/, /proc/<pid>/environ) in audit or access logs.

HashiCorp has released patches addressing this vulnerability: upgrade to Nomad Community Edition 2.0.4 or Nomad Enterprise 2.0.4, 1.11.8, or 1.10.14 depending on your deployed version. As an interim workaround, restrict job submission permissions to only fully trusted users and operators, reducing the pool of potential attackers. Additionally, implement network segmentation and monitoring on Nomad client systems to detect anomalous container namespace access patterns (HashiCorp Advisory, GitHub Advisory).

HashiCorp published an official security advisory (HCSEC-2026-19) disclosing the vulnerability and providing patched versions on July 8, 2026. The CISA Vulnerability Bulletin SB26-194 referenced the CVE, indicating routine tracking by US government cybersecurity authorities. No significant independent researcher commentary or notable social media discussion has been identified beyond standard vulnerability database aggregation (HashiCorp Advisory, CISA Bulletin).