CVE-2024-6717: HashiCorp Nomad and Nomad Enterprise 1.6.12 up to 1.7.9, and 1.8.1 archive unpacking during migration is vulne

Routine

HIGH 7.7UPGRADE

CVE-2024-6717 is a high-severity flaw (CVSS 7.7) affecting nomad. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	7.7 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.4% (top 67%)
CISA exploited list	No
Weakness	CWE-610
Published	2024-07-23
Last modified	2026-06-17

Publisher (CNA): HashiCorp Inc. · Vendor: hashicorp

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-07-23 01:15 UTCPublished CVE record published
2026-06-17 08:18 UTCUpdated Record last modified

hashicorp nomad UPGRADE

Affected: >= 1.7.0 and < 1.7.10 · 1.6.12 · 1.8.1

Fixed in: 1.7.10

Safe to downgrade to: a release before 1.6.12

1. Check installed version

apt-cache policy nomad || rpm -q nomad || nomad --version

2. UPGRADE to 1.7.10 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade nomad

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade nomad

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 1.6.12 (Debian / Ubuntu)

apt-cache madison nomad sudo apt install nomad=<VERSION_BEFORE_1.6.12> sudo apt-mark hold nomad

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list nomad sudo dnf downgrade nomad-<VERSION_BEFORE_1.6.12> sudo dnf versionlock add nomad

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-6717?

nomad: upgrade to 1.7.10. Exact commands for each OS are on this page.

Is CVE-2024-6717 being exploited?

CVE-2024-6717 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-6717 affect?

CVE-2024-6717 affects nomad. Severity is high (CVSS 7.7). 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

How urgent is CVE-2024-6717?

Priority 35/100. High severity

Related CVEs

CVE-2025-4922 HIGH 8.1 UPGRADE Nomad Community and Nomad Enterprise (“Nomad”) prefix-based ACL policy lookup can lead to incorrect rule appli
CVE-2025-3744 HIGH 7.6 UPGRADE Nomad Enterprise (“Nomad”) jobs using the policy override option are bypassing the mandatory sentinel policies
CVE-2025-1296 MEDIUM 6.5 UPGRADE Nomad Community and Nomad Enterprise (“Nomad”) are vulnerable to unintentional exposure of the workload identi
CVE-2025-0937 HIGH 7.1 UPGRADE Nomad Community and Nomad Enterprise ("Nomad") event stream configured with a wildcard namespace can bypass th
CVE-2024-7625 MEDIUM 5.8 UPGRADE In HashiCorp Nomad and Nomad Enterprise from 0.6.1 up to 1.6.13, 1.7.10, and 1.8.2, the archive unpacking proc

References

← Back to latest CVEs