Vulnerability · CVE-2026-64672
Terragrunt catalog predictable temp symlink clobber
Published Oct 15, 2026 · corrected/updated Oct 15, 2026 · evidence confidence high
### Summary Terragrunt's command clones each repository referenced in your catalog configuration into a temporary working directory. In affected versions, the clone path it derived was deterministic and sat under the shared system temporary directory, in the form . Because that path was predictable and Terragrunt followed a symlink already present there instead of rejecting it, a local attacker could plant a symlink at that path and cause Terragrunt to delete a directory and re-clone into it outside the intended temporary root. ### Impact This affected users who ran on a host they shared with other local users or processes they did not fully trust, such as a multi-user server or a shared CI runner. The attack required a local attacker: a separate local user or process able to write to the shared system temporary directory. It was not remotely exploitable, and the victim had to run while the attacker's symlink was already in place. Because the predictable path depended only on the repository URL being cataloged and the location of the system temporary directory, the attacker could compute it in advance and plant a symlink there before the victim ran the command. When the victim ran , Terragrunt followed the symlink out of the intended temporary root, deleted an existing directory under the attacker-chosen parent, and repopulated that path with the cloned repository contents. All of this happened in the security context of the user running Terragrunt. The attacker controlled the parent directory the symlink pointed to, but not the leaf name: the leaf was fixed to , derived from the repository URL the victim cataloged. The primitive was deletion of an existing directory outside the temporary root, followed by a re-clone into that same path. On a single-user machine with no hostile local processes, exposure was minimal. ### Affected Versions - Terragrunt ### Patches This vulnerability has been resolved in Terragrunt version . All users are strongly advised to upgrade. #
Grounded briefings
Catalog interpretations for three audiences. Each brief cites ingested metadata and the original advisories below. They are not independent research and they do not invent exploit steps.
Executive
CVE-2026-64672 is a medium public vulnerability record for this product. It is not currently listed in the CISA Known Exploited catalog. Check the linked vendor or CERT advisories for patch status. This summary is a catalog interpretation of the ingested metadata and cites the original advisories below.
System administrator
Identify whether this product is in your estate, then compare installed versions with the affected ranges. Affected packages or ranges on record: github.com/gruntwork-io/terragrunt (0 → 1.1.1); github.com/gruntwork-io/terragrunt (< 1.1.1); github.com. Check the linked vendor or CERT advisories for patch status. Prefer the vendor or distribution advisory linked in Sources before changing production systems. This is a catalog interpretation, not a runbook.
Security analyst
Signals on file: no CVSS/EPSS yet. It is not currently listed in the CISA Known Exploited catalog. Weakness classes: CWE-377, CWE-59. Sources contributing to this record: cve_org, github, gitlab, osv. Public exploit references, when present, are outbound links only and are not proof of active exploitation. This is a catalog interpretation of stored metadata.
Exploitation and remediation
Exploitation evidence
Not listed as known exploited in CISA KEV. Not in CISA KEV or VulnCheck KEV.
Patch and remediation
No required-action text is stored yet. Use the vendor or CERT links in Sources for patch availability.
Safe detection guidance
Compare installed versions with the affected ranges below and verify the advisory from the original publisher. This site stores metadata and outbound links only; it does not ship exploit code or proof-of-concept payloads.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Oct 15, 2026 · GitHub Advisory Database
Detected
### Summary Terragrunt's command clones each repository referenced in your catalog configuration into a temporary working directory. In affected versions, the clone path it derived was deterministic and sat under the shared system temporary directory, in the form . Because that path was predictable and Terragrunt followed a symlink already present there instead of rejecting it, a local attacker co
Oct 15, 2026 · GitHub Advisory Database
Updated
### Summary Terragrunt's command clones each repository referenced in your catalog configuration into a temporary working directory. In affected versions, the clone path it derived was deterministic and sat under the shared system temporary directory, in the form . Because that path was predictable and Terragrunt followed a symlink already present there instead of rejecting it, a local attacker co
Oct 15, 2026 · GitHub Advisory Database
Fix available
github.com/gruntwork-io/terragrunt fixed in 1.1.1
Oct 15, 2026 · GitHub Advisory Database
Fix available
github.com/gruntwork-io/terragrunt fixed in 1.1.1
Oct 15, 2026 · GitHub Advisory Database
Updated
### Summary Terragrunt's command clones each repository referenced in your catalog configuration into a temporary working directory. In affected versions, the clone path it derived was deterministic and sat under the shared system temporary directory, in the form . Because that path was predictable and Terragrunt followed a symlink already present there instead of rejecting it, a local attacker co
Affected
- Go github.com/gruntwork-io/terragrunt0 → 1.1.1
- go github.com/gruntwork-io/terragrunt< 1.1.1
- golang github.comversion unspecified
Sources
- CVE.orgVulnerability recordCVE-2026-64672
Official CVE identifier
cve.org - GitHub Advisory DatabasePackage advisoryGHSA-wv6g-x823-wx9m
GitHub Advisory Database record mirrored by OSV.
github.com - GitLab Advisory DatabasePackage advisoryCVE-2026-64672
Terragrunt's terragrunt catalog command clones each repository referenced in your catalog configuration into a temporary working directory. In affected versions, the clone path it derived was deterministic and sat under the shared system temporary directory, in the form /catalog- . Because that path was predictable and Terragrunt followed a symlink already present there instead of rejecting it, a
advisories.gitlab.com - OpenSSF OSV / OSV ScannerPackage advisoryGHSA-wv6g-x823-wx9m
Terragrunt catalog predictable temp symlink clobber
osv.dev