Link Following Affecting terragrunt package, versions <1.1.1-r0


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.18% (8th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-MINIMOSLATEST-TERRAGRUNT-21177973
  • published18 Oct 2026
  • disclosed3 Nov 2026

Introduced: 18 Oct 2026

CVE-2026-64672  (opens in a new tab)
CWE-59  (opens in a new tab)
CWE-377  (opens in a new tab)

How to fix?

Upgrade Minimos:latest terragrunt to version 1.1.1-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream terragrunt package and not the terragrunt package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

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.