What is the CVSS score of CVE-2026-14373?

CVE-2026-14373 has a CVSS 3.1 base score of 7.7 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N. EPSS exploitation probability: 0.2%.

Which versions of HashiCorp Nomad are affected by CVE-2026-14373?

HashiCorp Nomad and Nomad Enterprise contain a namespace escape vulnerability (CVE-2026-14373) allowing authenticated job submitters to bypass container isolation and access host and co-located…. A patch is available.

How to fix or mitigate CVE-2026-14373?

24 hours: Inventory all HashiCorp Nomad and Enterprise deployments; identify accounts with job submission permissions; enable audit logging for job submissions. 7 days: Restrict job submission access to trusted accounts only; disable Docker task driver if not operationally required; implement network segmentation to limit container egress to host systems and co-located services. 30 days: Contact HashiCorp for patch availability timeline; evaluate job execution environment isolation strategies; review job submission workflows to minimize privileged account exposure.

HashiCorp Nomad CVE-2026-14373

EUVD-2026-42349 HIGH

Missing Authorization (CWE-862)

2026-07-08 HashiCorp

GHSA-2cc5-jjc3-x9fw

Authentication Bypass Hashicorp Docker Nomad Nomad Enterprise

7.7

CVSS 3.1 · Vendor: HashiCorp

Severity by source

Vendor (HashiCorp) PRIMARY

7.7 HIGH

AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

vuln.today AI

7.7 HIGH

Authenticated job submitter (PR:L) sends a crafted job over the API (AV:N/AC:L); breaking container isolation to read host/co-tenant data is a scope change (S:C) with confidentiality-only impact.

3.1 AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N

Primary rating from Vendor (HashiCorp).

CVSS VectorVendor: HashiCorp

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Changed

Confidentiality

High

Integrity

None

Availability

None

Lifecycle Timeline

Patch available

Jul 08, 2026 - 21:04 EUVD

Analysis Generated

Jul 08, 2026 - 20:37 vuln.today

CVE Published

Jul 08, 2026 - 17:29 cve.org

HIGH 7.7

DescriptionCVE.org

HashiCorp Nomad and Nomad Enterprise did not enforce the allow_privileged restriction for the Docker task driver's host namespace mode options. This may allow an authenticated job submitter to run a container in a host namespace and access information belonging to the host or to other workloads on the same client. This vulnerability, CVE-2026-14373, is fixed in Nomad Community Edition 2.0.4 and Nomad Enterprise 2.0.4, 1.11.8, and 1.10.14.

Articles & Coverage 2

News 4 New HashiCorp Vulnerabilities - 1 Critical, 3 High, 1 With POC Jul 09, 2026 News 4 New Docker Vulnerabilities - 1 Critical, 3 High, 1 With POC Jul 09, 2026

AnalysisAI

Host namespace escape in HashiCorp Nomad and Nomad Enterprise lets an authenticated job submitter bypass the allow_privileged control for the Docker task driver, launching containers in host PID/network/IPC namespaces to read data from the host or co-located workloads on the same client node. The flaw stems from missing authorization enforcement (CWE-862) and carries a CVSS 7.7 with a changed scope, reflecting cross-tenant impact. There is no public exploit identified at time of analysis and it is not listed in CISA KEV.

Technical ContextAI

Nomad is a HashiCorp workload orchestrator that schedules containers and other tasks across a cluster of client nodes. Its Docker task driver supports host namespace mode options (equivalent to Docker's network_mode=host, pid_mode=host, and ipc_mode=host), which break container isolation by placing the container in the host's namespaces. The allow_privileged plugin/driver configuration is intended to gate such privileged capabilities so operators can forbid them cluster-wide. Per the CPE data (cpe:2.3:a:hashicorp:nomad and cpe:2.3:a:hashicorp:nomad_enterprise), both editions are affected. The root cause is CWE-862 (Missing Authorization): the driver failed to check the allow_privileged restriction against the host namespace mode options, so the intended policy boundary was never evaluated for those settings.

RemediationAI

Vendor-released patch: upgrade to Nomad Community Edition 2.0.4, or Nomad Enterprise 2.0.4, 1.11.8, or 1.10.14, matching your current release branch, per HashiCorp advisory HCSEC-2026-19 (https://discuss.hashicorp.com/t/hcsec-2026-19-nomad-docker-driver-vulnerable-to-host-namespace-bypass-on-linux/77557). Until you can patch, reduce exposure by tightening who can submit jobs: restrict Nomad ACL policies so that only trusted namespaces/operators hold submit-job capability, since the attack requires an authenticated submitter. As a compensating control you can also constrain the Docker driver configuration and job submissions to reject host namespace options (avoid network_mode=host, pid_mode=host, and ipc_mode=host in job specs) and use Sentinel policies (Enterprise) or admission controls to deny such jobs; note the trade-off that legitimate workloads relying on host networking or host PID/IPC will be blocked. Separating untrusted tenants onto dedicated client nodes further limits the blast radius of any successful host-namespace access.