CVE-2021-43415: Improper Authentication in HashiCorp Nomad

github.com/hashicorp/nomad Updated 02 Oct 2025

Summary

10/12/2021
Yes i
High
8.8

CVE-2021-43415: Improper Authentication in HashiCorp Nomad. Affects github.com/hashicorp/nomad across 3 version ranges.

< 1.0.14 >= 1.1.0, < 1.1.8 >= 1.2.0, < 1.2.1

Fixed in 1.0.14, 1.1.8 or 1.2.1, depending on the release line you run. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

HashiCorp Nomad is an open-source cluster manager and scheduler designed for microservices and batch applications. It allows users to deploy and manage applications across a distributed infrastructure. Nomad supports various task drivers, including the QEMU task driver, which enables running virtual machines as tasks. This vulnerability affects Nomad versions up to 1.0.13, 1.1.7, and 1.2.0 when the QEMU task driver is enabled.

Vulnerability Detail

The vulnerability in HashiCorp Nomad allows authenticated users with job submission capabilities to bypass the configured allowed image paths when using the QEMU task driver. This means that an attacker with the ability to submit jobs can execute arbitrary code by specifying an unauthorized image path. The impact of this vulnerability is high, as it allows unauthorized code execution within the Nomad environment.

How To Fix

Latest published version: v1.11.3 as of 22 Oct 2026

go get github.com/hashicorp/nomad@v1.11.3

Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.

If you can't move to the latest

The minimum fixed version depends on the release line you run.

  • < 1.0.14 1.0.14
    go get github.com/hashicorp/nomad@v1.0.14
  • >= 1.1.0, < 1.1.8 1.1.8
    go get github.com/hashicorp/nomad@v1.1.8
  • >= 1.2.0, < 1.2.1 1.2.1
    go get github.com/hashicorp/nomad@v1.2.1

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Workaround

As a workaround, users can disable the QEMU task driver if it is not required for their deployments. This can be done by modifying the Nomad configuration to remove or comment out the QEMU task driver configuration. Here is an example of how to disable the QEMU task driver:

task "example" {
  driver = "docker"
  config {
    image = "example/image"
  }
}

In the above configuration, the QEMU task driver is replaced with the Docker task driver. This ensures that only authorized Docker images can be used.

Conclusion

The vulnerability in HashiCorp Nomad allows authenticated users to bypass image path restrictions and execute unauthorized code when using the QEMU task driver. To mitigate this issue, it is crucial to upgrade to the latest patched versions of Nomad. Additionally, disabling the QEMU task driver can serve as a temporary workaround. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for github.com/hashicorp/nomad →

Share this vulnerability

FAQ

HashiCorp Nomad is an open-source cluster manager and scheduler designed for microservices and batch applications. It allows users to deploy and manage applications across a distributed infrastructure.

The QEMU task driver in Nomad enables running virtual machines as tasks. It provides a way to execute tasks using QEMU virtualization technology.

This vulnerability allows authenticated users with job submission capabilities to bypass the configured allowed image paths when using the QEMU task driver. It enables unauthorized code execution within the Nomad environment.

To fix this vulnerability, it is recommended to upgrade to the latest patched versions of HashiCorp Nomad. Upgrade to version 1.0.14 if using version 1.0.x, upgrade to version 1.1.8 if using version 1.1.x, and upgrade to version 1.2.1 if using version 1.2.x.

Yes, users can disable the QEMU task driver if it is not required for their deployments. This can be done by modifying the Nomad configuration to remove or comment out the QEMU task driver configuration.

Related vulnerabilities

Recent vulnerabilities recorded for github.com/hashicorp/nomad.

How To Fix

Latest published version: v1.11.3 as of 22 Oct 2026

go get github.com/hashicorp/nomad@v1.11.3

Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.

If you can't move to the latest

The minimum fixed version depends on the release line you run.

  • < 1.0.14 1.0.14
    go get github.com/hashicorp/nomad@v1.0.14
  • >= 1.1.0, < 1.1.8 1.1.8
    go get github.com/hashicorp/nomad@v1.1.8
  • >= 1.2.0, < 1.2.1 1.2.1
    go get github.com/hashicorp/nomad@v1.2.1

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback