# CVE-2026-64679: Atlantis: Path Traversal in Atlantis Workspace Handling Allows Out-of-Bounds Directory Deletion/Creation

> Attackers can exploit path traversal in Atlantis workspace handling to delete or create files outside intended directories, causing data loss or service disruption.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Aug 2026
- **Updated:** 25 Aug 2026
- **Also known as:** GHSA-26w5-6g95-gj28, GO-2026-6273, MINI-wp3h-677h-pcqr, MINI-xwcj-wg72-g25v

## What is CVE-2026-64679?

CVE-2026-64679 is a high-severity path traversal vulnerability in runatlantis atlantis, published on 21 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Atlantis is a self-hosted golang application that listens for Terraform pull request events via webhooks. From 0.19.8 until 0.45.0, Atlantis does not consistently validate user-controlled workspace values supplied through accepted repository-level atlantis.yaml configuration or authenticated /api/plan input before joining them into local workspace paths. Traversal segments can escape the intended per-pull workspace directory and cause clone preparation or other working-directory code paths to call os.RemoveAll, os.MkdirAll, or related filesystem operations on out-of-bounds directories before Terraform rejects the invalid workspace name. This can create, delete, or reuse writable paths with the privileges of the Atlantis process, causing integrity loss or denial of service. This issue is fixed in version 0.45.0.

Weakness: CWE-73 (External Control of File Name or Path), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

3 open source packages ship an affected version, including github.com/runatlantis/atlantis.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/runatlantis/atlantis` | Go | From 0.19.8 | 0.45.0 |
| `github.com/runatlantis/atlantis` | Go | From 0.19.8 | 0.45.0 |
| `github.com/runatlantis/atlantis` | Go | From 0.19.8 | 0.45.0 |

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

Upgrade github.com/runatlantis/atlantis to 0.45.0 or later.

## Is CVE-2026-64679 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-64679 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-64679 is a high-severity path traversal vulnerability in runatlantis atlantis, published on 21 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-64679 exists.

Affected packages and fixed versions:
- github.com/runatlantis/atlantis (Go): affected from 0.19.8; fixed in 0.45.0
- github.com/runatlantis/atlantis (Go): affected from 0.19.8; fixed in 0.45.0
- github.com/runatlantis/atlantis (Go): affected from 0.19.8; fixed in 0.45.0

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-64679/ (Markdown: https://insights.sbomify.com/CVE-2026-64679/index.md)
```

## Sources

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

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