# CVE-2026-45099: Terragrunt: Arbitrary File Deletion via Malicious Module Manifest

> A malicious module manifest allows arbitrary file deletion outside the cache, disrupting CI/CD pipelines and removing local source code.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Aug 2026
- **Updated:** 25 Aug 2026
- **Also known as:** GHSA-8394-6f8r-whxg, GO-2026-6241, MINI-hrq6-h952-wpqg, MINI-pv3f-2886-3ghh

## What is CVE-2026-45099?

CVE-2026-45099 is a medium-severity path traversal vulnerability in gruntwork-io terragrunt, published on 21 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Terragrunt is a flexible orchestration tool that allows Infrastructure as Code written in OpenTofu or Terraform to scale. Prior to 1.0.4, Terragrunt trusts paths decoded from a downloaded module's .terragrunt-module-manifest during fileManifest.Clean() in internal/util/file.go. A malicious or compromised external module can place absolute or traversal paths in the manifest, causing cleanup to delete files outside the module cache that are accessible to the Terragrunt process before OpenTofu or Terraform executes. This deletion-only primitive can remove local source code or configuration and disrupt CI/CD pipelines. This issue is fixed in version 1.0.4.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

3 open source packages ship an affected version, including github.com/gruntwork-io/terragrunt.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/gruntwork-io/terragrunt` | Go | All versions | 1.0.4 |
| `github.com/gruntwork-io/terragrunt` | Go | All versions | 1.0.4 |
| `github.com/gruntwork-io/terragrunt` | Go | All versions | 1.0.4 |

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

Upgrade github.com/gruntwork-io/terragrunt to 1.0.4 or later.

## Is CVE-2026-45099 being exploited?

There is no known exploitation of CVE-2026-45099 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-45099 and fix it if it is affected.

What it is: CVE-2026-45099 is a medium-severity path traversal vulnerability in gruntwork-io terragrunt, published on 21 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-45099 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/gruntwork-io/terragrunt (Go): affected all versions; fixed in 1.0.4
- github.com/gruntwork-io/terragrunt (Go): affected all versions; fixed in 1.0.4
- github.com/gruntwork-io/terragrunt (Go): affected all versions; fixed in 1.0.4

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-45099/ (Markdown: https://insights.sbomify.com/CVE-2026-45099/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-45099
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-45099
- OSV: https://osv.dev/vulnerability/CVE-2026-45099

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-45099/
Summaries are generated and may contain mistakes; the official description above is the record.