CVSS 4.0
4.4 mediumCVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:P/VC:N/VI:H/VA:H/SC:N/SI:N/SA:NCVE-2026-64672
Medium (4.4). EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/gruntwork-io/terragrunt 1.1.1.
On this page
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.
Severity
- EPSS
- 0.2% estimated probability of exploitation activity in the next 30 days; 7th percentile. Scored 2026-11-04. A forecast for this CVE across the internet, not for your own systems.
- CWEs
- CWE-59 Improper Link Resolution Before File Access (Link Following)
CWE-377 Insecure Temporary File deprecated by MITRE - OWASP Top 10
- A01:2025 Broken Access Control
- Published
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-64672 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-64672?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-64672?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-64672 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| gruntwork-io terragrunt | < 1.1.1 |
Packages (OSV)
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-wv6g-x823-wx9m | Go | github.com/gruntwork-io/terragrunt | <1.1.1 | 1.1.1 |
| GO-2026-6768 | Go | github.com/gruntwork-io/terragrunt | <1.1.1 | 1.1.1 |
Attack patterns (CAPEC)
- CAPEC-149 Explore for Predictable Temporary File Names Severity: Medium
- CAPEC-155 Screen Temporary Files for Sensitive Information Likelihood: Medium · Severity: Medium
- CAPEC-17 Using Malicious Files Likelihood: High · Severity: Very High
- CAPEC-35 Leverage Executable Code in Non-Executable Files Likelihood: High · Severity: Very High
- CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
- CAPEC-132 Symlink Attack Likelihood: Low · Severity: High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.