Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 4.4amended

Terragrunt catalog predictable temp symlink clobber

CVE-2026-64672GHSA-wv6g-x823-wx9m

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/gruntwork-io/terragrunt 1.1.1), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
4.4 · 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 · score source
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

Summary 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 <tmp/catalog-<base64 sha1 of the repo URL. 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 terragrunt catalog 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 terragrunt catalog while the…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 4 · amended ·

    Amended from ghsa record GHSA-wv6g-x823-wx9m

  2. Revision 3 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 2 · amended ·

    Amended from osv record GO-2026-6768

  4. Revision 1 · created ·

    Published from osv record GHSA-wv6g-x823-wx9m

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-64672

Advisory: Terragrunt catalog predictable temp symlink clobber
IDs: CVE-2026-64672, GHSA-wv6g-x823-wx9m
Record: https://patchnext.com/advisories/cve-2026-64672 (revision 4, source checked 26 Oct 2026, 15:32 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/gruntwork-io/terragrunt 1.1.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/gruntwork-io/terragrunt: affected < 1.1.1; fixed in 1.1.1

## Suggested inspection (read-only)
- Go github.com/gruntwork-io/terragrunt: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/gruntwork-io/terragrunt.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GO-2026-6768 (OSV record GO-2026-6768 lists affected ranges: Go github.com/gruntwork-io/terragrunt >=0 <1.1.1 (fixed))
- Verified: https://osv.dev/vulnerability/GHSA-wv6g-x823-wx9m (OSV record GHSA-wv6g-x823-wx9m lists affected ranges: Go github.com/gruntwork-io/terragrunt >=0 <1.1.1 (fixed))
- Verified: https://github.com/advisories/GHSA-wv6g-x823-wx9m (GitHub-reviewed advisory GHSA-wv6g-x823-wx9m lists affected ranges: Go github.com/gruntwork-io/terragrunt >=0 <1.1.1)

Commands are suggestions: review each one before running it.

Loading voting…