dbcve.org
Link Following (Symlink)Weakness · CWE-59

CVE-2026-14891

HIGH · 8.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 →
93/100
Remediation priority · Urgent
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 are vulnerable to a sandbox escape in the Docker task driver that may allow a job submitter to bind-mount a host path into a container even when volume bind mounts are disabled, potentially leading to reading and writing files on the host. This vulnerability, CVE-2026-14891, 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

A sandbox escape vulnerability in HashiCorp Nomad's Docker task driver allows a job submitter to bypass volume bind mount restrictions and mount arbitrary host paths into containers, enabling unauthorized read/write access to the host filesystem.

MitigationUpgrade Nomad to version 2.0.4 (Community), or 2.0.4/1.11.8/1.10.4 (Enterprise) to patch the Docker task driver sandbox bypass.

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
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/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. Identify Nomad installation and version
    Run 'nomad version' to obtain the installed Nomad version, or query the API at 'http://<nomad-address>:4646/v1/agent/leader' to retrieve version information from the running instance
    Affected if The installed version matches 1.10.x prior to 1.10.4, 1.11.x prior to 1.11.8, or 2.0.x prior to 2.0.4 (or any Enterprise version prior to those respective patches)
  2. Confirm Docker task driver is enabled
    Run 'nomad node status' to list client nodes, then 'nomad node info <node-id>' to inspect enabled drivers, or query the /v1/node/<node-id> API endpoint and inspect the 'Drivers' field
    Affected if The Docker driver shows 'DriverStatus': 'ready' or 'Enabled': true in the node driver information
  3. Check for bind mount volume configurations
    Examine Nomad job specification files (.nomad files) for 'volume_mount' blocks within task configurations, or query the /v1/allocations API to list running allocations and inspect their volume configurations
    Affected if Any job specification contains 'volume_mount' stanzas that bind host paths to containers using the Docker driver
  4. Inspect Docker volume driver configuration
    Review the Nomad client configuration file (commonly at /etc/nomad.d/nomad.hcl or /etc/nomad/config.hcl) for the 'docker' block and any 'volumes' or 'bind_volume' settings, or query the /v1/client/fs endpoint for running task volumes
    Affected if The Docker driver is configured with 'volumes' set to enable host path mounts (the default behavior allows bind mounts unless explicitly disabled)
  5. Verify host filesystem access from containers
    Submit a test job with a volume_mount referencing a known host path (e.g., '/etc' or '/root') and inspect the container to confirm the host path is accessible inside the container
    Affected if The container successfully mounts and exposes the specified host directory, demonstrating that arbitrary host path binding is not restricted

A user is affected if running a vulnerable Nomad version (pre-2.0.4/1.11.8/1.10.4) with the Docker task driver enabled and bind mount volumes configured, allowing jobs to mount arbitrary host paths into containers.

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 (Community), or 2.0.4/1.11.8/1.10.4 (Enterprise) to patch the Docker task driver sandbox bypass.

Recommended fix High confidence

Nomad Community Edition 2.0.4 or Nomad Enterprise 2.0.4/1.11.8/1.10.14

  1. Identify the current Nomad version running in the environment using 'nomad version'
  2. Determine whether using Nomad Community Edition or Enterprise Edition
  3. For Nomad Community Edition users: upgrade to version 2.0.4
  4. For Nomad Enterprise Edition users: upgrade to version 2.0.4, 1.11.8, or 1.10.14 (choose the version appropriate for your release line)
  5. After upgrading, verify the Docker task driver configuration does not allow unauthorized bind mounts
  6. Test that volume bind mount controls function as expected
Caveat Major version upgrades (1.x to 2.x) may include breaking changes; review Nomad 2.0 release notes before upgrading from 1.x

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-14891 — 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-14891 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