Terragrunt catalog predictable temp symlink clobber
- Exploited
- No known exploitation
- Fix
- Fixed in 1.1.1
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 1.1.1.
- Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
- Exposure?/25Exposure: unknown (data gap). No advisory context yet
- Reach?/20Reach: unknown (data gap). No tracked technology or package matched
- Severity4.4/10CVSS 4.4
- No patch0/5No signal
What would change the score
- Would score about 59 if added to CISA KEV
- Would score about 54 if CISA's SSVC rates exploitation active
- Would score about 26 if advisories confirm default setups are exposed
CVE-2026-64672 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 4.4 (medium) and affects terragrunt; fixed in 1.1.1.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 4/100 · provisional
- Fix
- Fixed in 1.1.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Terragrunt is a flexible orchestration tool that allows Infrastructure as Code written in OpenTofu or Terraform to scale. Prior to 1.1.1, the terragrunt catalog command derives a predictable per-repository catalog clone root under the shared system temporary directory and follows a symlink already placed at that path. A local attacker who can write to the temporary directory and predict the cataloged repository can redirect cleanup and cloning outside the intended root, causing an existing repository-named directory to be deleted and replaced in the victim's security context. The attack requires the victim to run terragrunt catalog on a shared host while the symlink is present, and it is not remotely exploitable. This issue is fixed in version 1.1.1.
What to do
Upgrade to a fixed version: 1.1.1.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- gruntwork-io terragrunt
fixed in 1.1.1
Evidence 4
- Advisory
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-64672
Is CVE-2026-64672 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-64672?
terragrunt: before 1.1.1.Source: cve.now feed data
How do I fix CVE-2026-64672?
Upgrade to a fixed version: 1.1.1.Source: cve.now feed data