CVE-2026-7474
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 · uneditedHashiCorp Nomad and Nomad Enterprise prior to 2.0.1 are vulnerable to code execution on the client host through a path traversal attack. This vulnerability (CVE-2026-7474) is fixed in Nomad 2.0.1, 1.11.5 and 1.10.11.
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 confidenceHashiCorp Nomad and Nomad Enterprise versions prior to 2.0.1 contain a path traversal vulnerability that allows authenticated operators to execute arbitrary code on client hosts through maliciously crafted file paths in job specifications.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Nomad installation and versionRun `nomad version` on the target host to retrieve the installed version of Nomad or Nomad EnterpriseAffected if The version shown is prior to 2.0.1, 1.11.5, or 1.10.11 (including any 1.x version below 1.10.11 or 1.11.x versions below 1.11.5)
-
Confirm this is a Nomad client nodeCheck the Nomad configuration file (commonly at /etc/nomad.d/nomad.hcl or /etc/nomad/config.hcl) for a `client` stanza with `enabled = true`, or run `nomad node status` to see if this host is registered as a clientAffected if The node is configured and enabled as a Nomad client (the vulnerability affects client hosts)
You are affected if this host runs Nomad client mode and the installed version is below 2.0.1 (or below 1.11.5/1.10.11 for older branches), allowing authenticated operators to submit jobs with malicious file paths that traverse to arbitrary locations on the client filesystem.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade Nomad to version 2.0.1, 1.11.5, or 1.10.11 (or later) to remediate the path traversal leading to code execution.
Nomad 2.0.1, 1.11.5, or 1.10.11 (choose based on your release branch)
- 1. Identify the current version of HashiCorp Nomad or Nomad Enterprise running in your environment
- 2. If running a version prior to 2.0.1, 1.11.5, or 1.10.11, plan for an upgrade to one of these fixed versions
- 3. Backup your Nomad configuration, data directory, and state before proceeding with the upgrade
- 4. Review the HashiCorp Nomad upgrade guides for your specific version path
- 5. Upgrade Nomad to version 2.0.1, 1.11.5, or 1.10.11 (or later) depending on your desired release branch
- 6. After upgrade, verify that the Nomad agent starts successfully and jobs can be scheduled
- 7. Test that the path traversal vulnerability is no longer present by ensuring job specifications cannot access files outside the allocated directory
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,520.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7474 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-7474 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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