CVE-2026-45099: Input Validation

Published Aug 17, 2026
·
Updated

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:

1. Strictly auditing the source URLs of all remote modules used in their Terragrunt configurations. 2. Only consuming modules from trusted, internally vetted sources or verified registries. 3. Pinning module versions to specific, known-safe Git commit SHAs rather than mutable tags or branches.

Technical Details

Terragrunt tracks files copied into a downloaded module's working directory using a .terragrunt-module-manifest file. During the directory cleanup process, Terragrunt decodes the entries in this manifest and removes the listed files to prepare a fresh directory for OpenTofu/Terraform runs.

Previously, Terragrunt trusted the manifest provided by the downloaded module without verifying that the paths scheduled for deletion remained within the boundaries of the module's destination directory. An attacker could forge a manifest containing directory traversal paths, causing the cleanup function to target files outside the cache. The patch introduces a secure boundary check to ensure all cleaned paths remain safely isolated inside the intended manifest folder.

Credit

Terragrunt would like to thank Francesco Sabiu (@fsabiu) for discovering and responsibly disclosing this vulnerability.

Affected Software

1 affected componentFixes available
go/github.com/gruntwork-io/terragrunt<1.0.4
1.0.4

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade go/github.com/gruntwork-io/terragrunt to a version that resolves this vulnerability.

    Fixed in 1.0.4
  2. Upgrade

    Upgrade terragrunt to a version that resolves this vulnerability.

    Fixed in v1.0.4
  3. Compensating control

    If you cannot upgrade immediately (Terragrunt < v1.0.4), mitigate by only consuming remote modules from trusted, internally vetted sources or verified registries.

  4. Compensating control

    If you cannot upgrade immediately (Terragrunt < v1.0.4), mitigate by pinning module versions to specific, known-safe Git commit SHAs instead of mutable tags or branches.

  5. Compensating control

    If you cannot upgrade immediately (Terragrunt < v1.0.4), mitigate by strictly auditing the source URLs of all remote modules used in your Terragrunt configurations.

Event History

Aug 17, 2026
Advisory Published
via GitHub·04:37 PM
Data Sourced
via GitHub·04:37 PM
DescriptionWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-45099?

CVE-2026-45099 is rated with a risk score of 40.

2

What vulnerability does CVE-2026-45099 expose in Terragrunt?

CVE-2026-45099 exposes an arbitrary file deletion flaw when downloading external modules.

3

How can I prevent exploitation of CVE-2026-45099?

To prevent exploitation of CVE-2026-45099, ensure that external modules do not contain maliciously crafted '.terragrunt-module-manifest' files.

4

Which versions of Terragrunt are affected by CVE-2026-45099?

CVE-2026-45099 affects versions of Terragrunt prior to the fix implemented in version 1.0.4.

5

How do I fix CVE-2026-45099?

To fix CVE-2026-45099, update Terragrunt to version 1.0.4 or later.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203