Path Traversal in github.com/hashicorp/nomad (CVE-2026-7474)
Summary
Path traversal in github.com/hashicorp/nomad (CVE-2026-7474). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 1.11.0-rc.1.0.20260511152149-cd7240c4099a or later.
Original description
The description as published by the source.
HashiCorp 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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-7474 has been found in github.com/hashicorp/nomad.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: upgrade github.com/hashicorp/nomad to 1.11.0-rc.1.0.20260511152149-cd7240c4099a or later.
If unsure, ask your IT team or search "github.com/hashicorp/nomad CVE-2026-7474" on the vendor's site.
CVE-2026-7474 (github.com/hashicorp/nomad) — CWE-22 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Patched: 1.11.0-rc.1.0.20260511152149-cd7240c4099a — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in github.com/hashicorp/nomad.
Check the vendor advisory for the affected versions of github.com/hashicorp/nomad.
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.
Update to 1.11.0-rc.1.0.20260511152149-cd7240c4099a.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/hashicorp/nomad' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/hashicorp/nomad' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/hashicorp/nomadを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/hashicorp/nomad to 1.11.0-rc.1.0.20260511152149-cd7240c4099aステージング環境で 1.11.0-rc.1.0.20260511152149-cd7240c4099a に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Ubuntu UBUNTU-CVE-2026-7474 nomad
References
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web discuss.hashicorp.com
- web github.com
- web github.com