Quick answers
- Is CVE-2026-14373 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-14373 being exploited in the wild.
- How severe is CVE-2026-14373?
- High severity, with a CVSS score of 7.7, published 8 July 2026.
- Which products and versions are affected?
- HashiCorp Nomad 0.4.1 to 2.0.3; HashiCorp Nomad Enterprise 0.4.1 to 2.0.3, 1.11.0 to 1.11.7, 1.10.0 to 1.10.13.
- Is there a fix for CVE-2026-14373?
- A patch was published on 2026-07-08. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-14373 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-14373?
- Check whether you run HashiCorp Nomad or HashiCorp Nomad Enterprise at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A missing authorization check (CWE-862) in the Nomad Docker task driver allows authenticated job submitters to bypass the 'allow_privileged' configuration. By specifying host namespace modes (PID, IPC, user, or UTS) in a job specification, an attacker can run a container within the host's namespace even when such privileges are explicitly disabled by the administrator. This enables the container to enumerate host processes and access sensitive environment variables or credentials belonging to the Nomad agent or other workloads. The vulnerability specifically affects Linux-based clients; Windows containers are not impacted. Patches are available in versions 2.0.4, 1.11.8, and 1.10.14.
Affected products
- HashiCorp Nomad 0.4.1 to 2.0.3
- HashiCorp Nomad Enterprise 0.4.1 to 2.0.3, 1.11.0 to 1.11.7, 1.10.0 to 1.10.13
Timeline
- 2026-07-08: disclosed
- 2026-07-08: advisory
- 2026-07-08: patched