CVE-2026-64679: Atlantis path traversal in workspace handling

CVE-2026-64679 · Severity: high · CVSS 8.1 · Published 2026-08-21

Atlantis is a Terraform pull request automation tool that manages infrastructure-as-code deployments. An attacker with repository access or API authentication can inject path traversal sequences into workspace configuration, causing Atlantis to create, modify, or delete directories outside its intended workspace boundaries. This could lead to loss of data, service disruption, or manipulation of the host system's filesystem.

Technologies: github.com/runatlantis/atlantis (Go). Vendors: Go.

Quick answers

Is CVE-2026-64679 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-64679 being exploited in the wild.
How severe is CVE-2026-64679?
High severity, with a CVSS score of 8.1, published 21 August 2026.
Which products and versions are affected?
github.com/runatlantis/atlantis (Go) >= 0.19.8, < 0.45.0, SEMVER:introduced=0.19.8,fixed=0.45.0.
Is there a fix for CVE-2026-64679?
Yes. github.com/runatlantis/atlantis (Go): upgrade to 0.45.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-64679 attacked?
It is attacked over the network.
Am I affected by CVE-2026-64679?
Check whether you run github.com/runatlantis/atlantis (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/runatlantis/atlantis (Go): upgrade to 0.45.0 or later
    go get github.com/runatlantis/atlantis@v0.45.0

Technical details

The vulnerability is a classic path traversal (CWE-22) caused by insufficient input validation of the workspace parameter before it is joined into filesystem paths. An attacker can supply a workspace value such as "../../../../../../../../tmp/f1-canary" through repository-level atlantis.yaml configuration or via an authenticated /api/plan request. Atlantis then resolves this path and uses it for working-directory operations including os.RemoveAll() and os.MkdirAll() calls, allowing the attacker to create or delete directories outside the intended ~/.atlantis/repos/ hierarchy. The attack requires low privilege (repository access or API authentication) and network access. Terraform eventually rejects the invalid workspace name, but only after Atlantis has already performed the filesystem operations, making the window for exploitation unavoidable. The fix is available in Atlantis 0.45.0.

Affected products

  • RunAtlantis Atlantis >= 0.19.8, < 0.45.0

Identifiers

  • CVE-2026-64679
  • GHSA-26w5-6g95-gj28
  • GO-2026-6273

Timeline

  • 2026-07-02: disclosed: Vulnerability published to GitHub Advisory Database (CVE-2026-64679)
  • 2026-07-02: patched: Fix released in Atlantis 0.45.0
  • 2026-08-21: advisory: Advisory reviewed and published to GitHub Advisory Database

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.