Path Traversal in github.com/gruntwork-io/terragrunt (CVE-2026-45099)
Summary
Path traversal in github.com/gruntwork-io/terragrunt (CVE-2026-45099). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.0.4 or later.
Original description
The description as published by the source.
Summary
Terragrunt is vulnerable to an arbitrary file deletion flaw when downloading external modules. If a remote module contains a maliciously crafted .terragrunt-module-manifest file, Terragrunt can be tricked into deleting files anywhere on the local filesystem that the Terragrunt process has access to.
Impact
This vulnerability impacts users who download and run untrusted or compromised OpenTofu/Terraform modules. The file deletion occurs during the module download and initialization phase, meaning it happens before OpenTofu or Terraform executes.
In a CI/CD environment or automated runner, an attacker-controlled module could delete arbitrary files, causing denial of service in the deployment pipeline. In a local environment, it could lead to the loss of local source code or configuration files.
This vulnerability is a deletion-only primitive; it does not directly allow for arbitrary code execution (RCE) or data exfiltration.
Affected Versions
- Terragrunt <
v1.0.4
Patches
This vulnerability has been resolved in Terragrunt version v1.0.4.
All users are strongly advised to upgrade.
Workarounds
If users cannot upgrade immediately, they can mitigate this risk by:
- Strictly auditing the source URLs of all remote modules used in their Terragrunt configurations.
- Only consuming modules from trusted, internally vetted sources or verified registries.
- Pinning module versions to specific, known-safe Git commit SHAs rather than mutable…
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-45099 has been found in github.com/gruntwork-io/terragrunt.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/gruntwork-io/terragrunt to 1.0.4 or later.
If unsure, ask your IT team or search "github.com/gruntwork-io/terragrunt CVE-2026-45099" on the vendor's site.
CVE-2026-45099 (github.com/gruntwork-io/terragrunt) — CWE-22
Patched: 1.0.4 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in github.com/gruntwork-io/terragrunt.
Check the vendor advisory for the affected versions of github.com/gruntwork-io/terragrunt.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.0.4.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/gruntwork-io/terragrunt' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/gruntwork-io/terragrunt' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/gruntwork-io/terragruntを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/gruntwork-io/terragrunt to 1.0.4ステージング環境で 1.0.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- package github.com
- web github.com
- web github.com
- web github.com
- web security-advisories@github.com
- web security-advisories@github.com