CVE-2026-107347: Nomad dispatch payload writes can escape the allocation directory through symlinks

Published Oct 29, 2026
·
Updated

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.0 and Nomad Enterprise 2.1.0, 1.11.12, and 1.10.18.

Other sources

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.

— NVD

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade HashiCorp Nomad to a version that resolves this vulnerability.

    Fixed in 2.1.1
  2. Upgrade

    Upgrade HashiCorp Nomad Enterprise to a version that resolves this vulnerability.

    Fixed in 2.1.0
  3. Upgrade

    Upgrade HashiCorp Nomad Enterprise to a version that resolves this vulnerability.

    Fixed in 1.11.12
  4. Upgrade

    Upgrade HashiCorp Nomad Enterprise to a version that resolves this vulnerability.

    Fixed in 1.10.18

Event History

Oct 29, 2026
CVE Published
via MITRE·06:10 PM
Data Sourced
via MITRE·06:10 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

What level of access does an attacker need to exploit this issue?

An attacker needs the ability to run or control a malicious workload. The vulnerability is triggered through symlink following during dispatch payload or executor log writes.

2

When could this result in host-level root code execution?

The malicious workload may modify files outside its allocation directory. If the Nomad client agent runs as root, this could lead to code execution as root on the client host.

3

Which releases are reported as fixed?

Nomad Enterprise fixes are listed as 2.1.0, 1.11.12, and 1.10.18. The provided data is inconsistent for the Nomad community release, listing both 2.1.0 and 2.1.1 as the fixed version; verify the applicable advisory before selecting an upgrade target.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203