NomadApplication · Hashicorp

CVE-2021-41865

MEDIUM · 6.5 CVSS v3.1 Published 2021-10-07
Fix available
A fix is available. Upgrade to 1.1.6 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 1.1.1 through 1.1.5 allowed authenticated users with job submission capabilities to cause denial of service by submitting incomplete job specifications with a Consul mesh gateway and host networking mode. Fixed in 1.1.6.

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

This is a denial of service vulnerability in HashiCorp Nomad where authenticated users with job submission capabilities can submit incomplete job specifications using Consul mesh gateway with host networking mode, causing the Nomad cluster to become unstable or unavailable.

MitigationUpgrade to Nomad version 1.1.6 or later. As a compensating control, restrict or carefully audit job submission permissions for untrusted users until the upgrade can be completed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
NomadApplication
Affected:>= 1.1.1, < 1.1.6

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

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. Check Nomad server version
    Run `nomad version` on the Nomad server nodes to obtain the installed version.
    Affected if The installed version is >= 1.1.1 and < 1.1.6.
  2. Verify job submission is enabled
    Review Nomad ACL policies and examine the server configuration for job submission permissions. Check if anonymous or untrusted users have `submit-job` capabilities.
    Affected if Untrusted or anonymous users have job submission capabilities.
  3. Confirm Consul mesh gateway usage
    Inspect submitted job specifications for `connect` blocks using ` Consul mesh gateway ` with `network_mode = host`. Review job files or query running jobs via `nomad job inspect <job_id>`.
    Affected if Jobs are using Consul mesh gateway with host networking mode.
  4. Identify users with job submission privileges
    Use `nomad acl policy list` and `nomad acl token list` to enumerate tokens and policies that grant job submission capabilities.
    Affected if Multiple users or tokens exist with job submission capabilities.

You are affected if your Nomad version is between 1.1.1 and 1.1.5 inclusive and users with job submission permissions can submit jobs using Consul mesh gateway with host networking mode.

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
Upgrade available Upgrade to 1.1.6 or later
Fixed in 1.1.6
Interim mitigation

Upgrade to Nomad version 1.1.6 or later. As a compensating control, restrict or carefully audit job submission permissions for untrusted users until the upgrade can be completed.

Recommended fix High confidence

Nomad 1.1.6

  1. Back up Nomad data directory and configuration files
  2. Stop the Nomad service
  3. Download Nomad version 1.1.6 from the official HashiCorp releases (https://www.nomadproject.io/downloads)
  4. Replace the existing Nomad binary with the 1.1.6 version
  5. Review the Nomad 1.1.6 changelog for any required configuration changes or migration steps
  6. Start the Nomad service
  7. Verify Nomad is running version 1.1.6 using 'nomad version'
Caveat Review Nomad 1.1.6 release notes for any breaking changes between your current version and 1.1.6; minor version upgrades typically preserve configuration compatibility

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

Fix this in Nomad Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-41865 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-2021-41865 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