# Terragrunt: Arbitrary File Deletion via Malicious Module Manifest

Advisory record · `GHSA-8394-6f8r-whxg`

- **Identifiers:** `GHSA-8394-6f8r-whxg` · `CVE-2026-45099` · `GO-2026-6241`
- **State:** Confirmed
- **Severity:** CVSS 6.9 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-20](https://cwe.mitre.org/data/definitions/20.html) · [CWE-22](https://cwe.mitre.org/data/definitions/22.html)
- **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md) · [CWE-20](https://agentprime.io/advisories/tag/cwe-20.md)
- **Published:** 17 Aug 2026
- **Updated:** 18 Aug 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 17 Aug 2026, 16:37 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/gruntwork-io/terragrunt` (Go): affected `<1.0.4`; fixed in `1.0.4`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Terragrunt versions before 1.0.4 can delete arbitrary files on the local filesystem during module download when a remote module contains a maliciously crafted .terragrunt-module-manifest file. An attacker who gets Terragrunt to use an untrusted module can cause deletion of files the Terragrunt process can access, which may disrupt CI/CD pipelines or lose local files. Upgrade to Terragrunt 1.0.4, which fixes the issue; until then, audit remote module sources and use only trusted modules pinned to known commit SHAs.

Written 6 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 6.9 Medium, CVSS 4.0: `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`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0054, the 46th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:52 UTC: First seen by agentprime
- 31 Oct 2026, 14:52 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-8394-6f8r-whxg)

## Sources

- [GitHub Advisory Database: GHSA-8394-6f8r-whxg](https://github.com/advisories/GHSA-8394-6f8r-whxg)
- [OSV: GHSA-8394-6f8r-whxg](https://osv.dev/vulnerability/GHSA-8394-6f8r-whxg)
- <https://github.com/gruntwork-io/terragrunt/security/advisories/GHSA-8394-6f8r-whxg>
- <https://github.com/gruntwork-io/terragrunt>
- <https://github.com/gruntwork-io/terragrunt/releases/tag/v1.0.4>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-8394-6f8r-whxg>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-8394-6f8r-whxg/>. Everything for agents: <https://agentprime.io/llms.txt>.