Read the docs

Symlink following in HashiCorp Nomad allows writes outside allocation

Priority LOW 35CWE-59Published · Updated

Key facts

Attack vector
Local
Privileges required
Low
User interaction
None
Attack complexity
Low
Impact type
—
Confidentiality · integrity · availability
None · High · High
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA.

Summary

HashiCorp Nomad from 0.3.0 before 2.1.1 and Nomad Enterprise from 0.3.0 before 2.1.0 are affected. They follow symlinks during dispatch payload and executor log writes (CWE-59). A malicious workload can modify files outside its allocation directory, and when the client agent runs as root this can lead to code execution as root on the client host.

Written with Claude Haiku 5.5 from the sources below · 2026-11-05

Description from the CNA

HashiCorp Nomad and Nomad Enterprise are vulnerable to symlink following during dispatch payload and executor log writes that may allow a malicious workload to modify files outside its allocation directory. When the client agent runs as root, this could lead to code execution as root on the client host. This vulnerability (CVE-2026-107347) is fixed in Nomad 2.1.1 and Nomad Enterprise 2.1.0, 1.11.12, and 1.10.18.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00132 2nd percentileScored 2026-11-07
Fix Fixed Nomad (HashiCorp): 2.1.1Nomad Enterprise (HashiCorp): 2.1.0

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
HashiCorpNomad0.3.0 to before 2.1.12.1.1Patch availableCNA
HashiCorpNomad Enterprise0.3.0 to before 2.1.02.1.0Patch availableCNA
  • Nomad VendorHashiCorp Affected 0.3.0 to before 2.1.1 Fixed in 2.1.1 Patch available CNA
  • Nomad Enterprise VendorHashiCorp Affected 0.3.0 to before 2.1.0 Fixed in 2.1.0 Patch available CNA

Remediation

Upgrade Nomad to 2.1.1. Upgrade Nomad Enterprise to 2.1.0, 1.11.12 or 1.10.18.

Written with Claude Haiku 5.5 from the sources below · 2026-11-05

  • Fix · CNA Nomad (HashiCorp) Fixed in 2.1.1
  • Fix · CNA Nomad Enterprise (HashiCorp) Fixed in 2.1.0

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    HashiCorp Nomad, Nomad Enterprise 2.1.0, 2.1.1

    3 records Highest priority Priority LOW 3 LOW

    Other records, highest priority first

    • TI-2026-82717 Symlink following in Nomad lets workloads alter host permissionsPriority LOW 39
    • TI-2026-82714 Nomad API endpoints leak cross-namespace informationPriority LOW 19

Timeline

  1. 2026-10-29 Threatist record created from CVE-2026-107347
  2. 2026-10-29 Alias added: GHSA-qx6c-5f28-88p2
  3. 2026-10-30 Fix available: HashiCorp/[email protected] · CNA
  4. 2026-10-30 CISA SSVC decision points changed
  5. 2026-10-30 Priority changed: MEDIUM → LOW

References

  • TI-2024-01904 Vault Cert Auth Method Did Not Correctly Validate Non-CA Certificates CVSS 3.1CRITICAL 9.8
  • TI-2021-18437 HashiCorp Consul Enterprise before 1.8.17, 1.9.x before 1.9.11, and 1.10.x before 1.10.4… CVSS 3.1HIGH 8.8
  • TI-2026-06570 Nomad vulnerable to path traversal in dynamic host volume which may lead to code execution CVSS 3.1HIGH 8.8
  • TI-2020-17753 The official Consul Docker images 0.7.1 through 1.4.2 contain a blank password for a root… CVSS 3.1CRITICAL 9.8
  • TI-2026-13641 consul-mcp-server vulnerable to cross-tenant credential reuse in streamable-HTTP stateless mode CVSS 3.1CRITICAL 10.0
  • TI-2026-13778 terraform-mcp-server vulnerable to cross-tenant credential reuse in streamable-HTTP stateless mode CVSS 3.1CRITICAL 10.0
See all 246 →

Sources