PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-64679 runatlantis CVE debrief

Atlantis, a self-hosted golang application, is vulnerable to a path traversal attack. This occurs due to inconsistent validation of user-controlled workspace values supplied through accepted repository-level atlantis.yaml configuration or authenticated /api/plan input. The vulnerability allows an attacker to create, delete, or reuse writable paths with the privileges of the Atlantis process, potentially leading to integrity loss or denial of service. The issue affects Atlantis versions 0.19.8 to 0.45.0 and is fixed in version 0.45.0. Users should review the official advisory and CVE record to validate affected scope, severity, and vendor guidance.

Vendor
runatlantis
Product
atlantis
CVSS
HIGH 8.1
CISA KEV
Not listed in stored evidence
Original CVE published
2026-08-21
Original CVE updated
2026-09-09
Advisory published
2026-08-21
Advisory updated
2026-09-09

Who should care

Users of Atlantis versions 0.19.8 to 0.45.0 should be aware of this vulnerability and take necessary actions to mitigate it. Affected operators, platforms, and security teams should review the official advisory and CVE record to validate affected scope, severity, and vendor guidance. They should also plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.

Technical summary

The vulnerability exists due to inconsistent validation of user-controlled workspace values in Atlantis versions 0.19.8 to 0.45.0. This allows an attacker to perform a path traversal attack, potentially leading to integrity loss or denial of service. The issue is fixed in version 0.45.0. Affected operators should review compensating controls for exposed systems while remediation is scheduled and verified.

Defensive priority

High priority due to potential for integrity loss and denial of service

Recommended defensive actions

  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
  • Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
  • Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
  • Review compensating controls for exposed systems while remediation is scheduled and verified.
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review.
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented.
  • Inventory and verify Atlantis version

Evidence notes

Evidence is limited; primary official records indicate a path traversal vulnerability in Atlantis versions 0.19.8 to 0.45.0. The issue is fixed in version 0.45.0. To verify, defenders should review the official advisory and CVE record for affected scope, severity, and vendor guidance. They should also check relevant monitoring, detection, and logs for exposed assets that need extra review.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-64679 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-64679

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-64679 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-64679

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.