HashiCorp Nomad prior 2.1.0/1.11.12/1.10.18 Dispatch link following
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 1.14 |
Summary
A vulnerability, which was classified as problematic, has been found in HashiCorp Nomad. The affected element is an unknown function of the component Dispatch. Performing a manipulation results in link following. This vulnerability is cataloged as CVE-2026-107347. The attack must be initiated from a local position. There is no exploit available. It is advisable to upgrade the affected component.
Details
A vulnerability, which was classified as problematic, was found in HashiCorp Nomad. This affects an unknown functionality of the component Dispatch. The manipulation with an unknown input leads to a link following vulnerability. CWE is classifying the issue as CWE-59. The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource. This is going to have an impact on integrity, and availability. The summary by CVE is:
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.
The advisory is shared at discuss.hashicorp.com. This vulnerability is uniquely identified as CVE-2026-107347 since 10/07/2026. The exploitability is told to be easy. An attack has to be approached locally. Neither technical details nor an exploit are publicly available.
Upgrading to version 2.1.0, 1.11.12 or 1.10.18 eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.3
VulDB Base Score: 4.4
VulDB Temp Score: 4.2
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 8.4
CNA Vector (HashiCorp): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Link followingCWE: CWE-59
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Nomad 2.1.0/1.11.12/1.10.18
Timeline
10/07/2026 CVE reserved10/29/2026 Advisory disclosed
10/29/2026 VulDB entry created
10/29/2026 VulDB entry last update
Sources
Advisory: discuss.hashicorp.comStatus: Confirmed
CNA: HashiCorp
CVE: CVE-2026-107347 (🔒)
GCVE (CVE): GCVE-0-2026-107347
GCVE (VulDB): GCVE-100-428709
Entry
Created: 10/29/2026 19:26Changes: 10/29/2026 19:26 (62)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.