Directory integrity loss via workspace path traversal
Published Aug 21, 2026 · Updated Aug 25, 2026
Path traversal in Atlantis 0.19.8 through 0.44.1 allows remote authenticated users to alter or delete writable directories. Workspace handling joins unvalidated traversal segments from atlantis.yaml or /api/plan input into local paths before calling directory creation or recursive removal operations. Reachability requires accepted repository configuration or authenticated API access, and impact is bounded by the Atlantis process's writable paths.
Summary
What happened
Path traversal in Atlantis 0.19.8 through 0.44.1 allows remote authenticated users to alter or delete writable directories. Workspace handling joins unvalidated traversal segments from atlantis.yaml or /api/plan input into local paths before calling directory creation or recursive removal operations. Reachability requires accepted repository configuration or authenticated API access, and impact is bounded by the Atlantis process's writable paths.
The record
- CVE
- CVE-2026-64679
- Published
- Aug 21, 2026
- Updated
- Aug 25, 2026
- Vendor
- runatlantis
- Product
- Atlantis
- Classifications
- CWE-22, CWE-73, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 21, 2026CVE publishedPublication date reported by the CVE source.
- Aug 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 0.19.8, < 0.45.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Repository-level atlantis.yaml workspace traversal proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo