CVE-2026-64679
Directory-traversal in Atlantis lets workspace names trigger filesystem operations outside intended dirs.
Is CVE-2026-64679 being exploited?
Not confirmed. CVE-2026-64679 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.60% probability of exploitation in the next 30 days.
How severe is CVE-2026-64679?
CVE-2026-64679 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-64679?
Yes. A fix has been recorded for CVE-2026-64679. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-64679 affect?
CVE-2026-64679 affects Atlantis 0.19.8 - 0.44.0, Self-hosted Atlantis deployments, Terraform webhook integrations using Atlantis. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-64679?
Upgrade Atlantis to >=0.45.0; restrict process privileges and validate workspace inputs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Crafted workspace names can cause Atlantis to create/delete/reuse filesystem paths as the Atlantis process, enabling integrity loss or DoS.
Immediate action required
- affected>= 0.19.8 and < 0.45.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.