dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-14373

HIGH · 7.7 CVSS v3.1 Published 2026-07-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
83/100
Remediation priority · High
Remotely reachable Zero-click 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

HashiCorp Nomad's Docker task driver failed to enforce the allow_privileged setting when containers requested host namespace mode, allowing authenticated job submitters to bypass the privilege restriction and run containers with host namespace access. This enables container escape to view host resources and cross-workload data exposure.

MitigationUpgrade Nomad to version 2.0.4 (CE or Enterprise), 1.11.8, or 1.10.14. If immediate upgrade is not possible, audit job specifications to prevent host namespace mode usage and review ACL policies for job submission permissions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Nomad version
    Run `nomad version` on the Nomad server/agent nodes to obtain the installed version string.
    Affected if The installed version is lower than 2.0.4, 1.11.8, or 1.10.14 (or is a prerelease/beta of 2.0.x below 2.0.4).
  2. Verify Docker task driver is enabled
    Check the Nomad client configuration (usually in /etc/nomad.d/nomad.hcl or via `nomad agent-info` output) for `plugin = "docker"` or review the plugins list from `nomad plugin list`.
    Affected if The Docker task driver is enabled and running on Nomad clients.
  3. Inspect allow_privileged configuration
    Review the Nomad client configuration file and look for the `allow_privileged` setting within the Docker plugin stanza (docker { allow_privileged = <value> }). Also check `nomad plugin status docker`.
    Affected if allow_privileged is set to false (the intended restriction) or is not explicitly set (defaults may vary).
  4. Review job specifications for host namespace mode
    Run `nomad job status` to list all jobs, then inspect job specs with `nomad job inspect <job-id>` or review job specification files for container mode settings such as `host_pid = true`, `host_network = true`, or `ipc_namespace_mode = "host"`.
    Affected if Any job specification contains host namespace mode directives (host_pid, host_network, ipc_namespace_mode=host, or similar).
  5. Audit ACL policies for job submission
    Review ACL policies using `nomad acl policy list` and inspect policies that grant `submit-job` capabilities. Check if untrusted users or broad groups can submit jobs.
    Affected if ACL policies permit job submission by authenticated users who should not have privileged container execution rights.

A user is affected if running a vulnerable Nomad version (below 2.0.4/1.11.8/1.10.14) with the Docker driver enabled, where allow_privileged is false or unset and any submitted jobs can request host namespace mode access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Nomad to version 2.0.4 (CE or Enterprise), 1.11.8, or 1.10.14. If immediate upgrade is not possible, audit job specifications to prevent host namespace mode usage and review ACL policies for job submission permissions.

Recommended fix High confidence

Nomad Community Edition 2.0.4, Nomad Enterprise 2.0.4, 1.11.8, or 1.10.14 (depending on current version)

  1. 1. Identify current Nomad version by running `nomad version` on all Nomad server and client nodes.
  2. 2. Determine which upgrade path applies based on current version: if on 2.x upgrade to 2.0.4, if on 1.11.x upgrade to 1.11.8, if on 1.10.x upgrade to 1.10.14.
  3. 3. Download the appropriate Nomad package from https://www.nomadproject.io/downloads.
  4. 4. On all Nomad server nodes, upgrade Nomad following the standard upgrade procedure: stop the Nomad service, replace the binary, restart the service.
  5. 5. On all Nomad client nodes, upgrade Nomad: stop the Nomad service, replace the binary, restart the service.
  6. 6. Verify the cluster is healthy using `nomad server members` and `nomad node status`.
  7. 7. Verify the fix is applied by attempting to submit a job with host namespace mode to confirm the allow_privileged restriction is now enforced.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-14373 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-14373 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data