When Atlantis performs workspace setup, it executes filesystem operations such as os.RemoveAll and os.MkdirAll on the resolved path before delegating to Terraform. Because these operations are executed with the permissions of the Atlantis process user, an authenticated user or an attacker capable of submitting a PR with a malicious atlantis.yaml can trigger unintended directory creation, deletion, or modification on the host system or within mounted container volumes. The issue is addressed in Atlantis version 0.45.0.

Impact

Successful exploitation allows unauthorized manipulation of the filesystem within the context of the Atlantis process. This can lead to the deletion of critical local data, unauthorized creation of directories, or the reuse of arbitrary paths during Terraform execution. While containerization may mitigate host-wide impacts, persistent volumes and internal Atlantis data paths remain exposed. This vulnerability poses significant integrity and denial-of-service risks to organizations relying on Atlantis for Infrastructure as Code automation.

Recommendation

• Upgrade Atlantis to version 0.45.0 or later immediately to resolve CVE-2026-64679.
• Audit repository-level atlantis.yaml files for any suspicious workspace parameter values containing directory traversal sequences.
• Restrict the permissions of the user account running the Atlantis service to the minimum required for its operation, ensuring it cannot modify sensitive system directories.
• Implement monitoring for unexpected directory deletion or creation events occurring within the application's working directories.