Directory Traversal Affecting atlantis-fips package, versions <0.45.0-r0


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.38% (32nd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-MINIMOSLATEST-ATLANTISFIPS-19232243
  • published23 Aug 2026
  • disclosed21 Aug 2026

Introduced: 21 Aug 2026

NewCVE-2026-64679  (opens in a new tab)
CWE-22  (opens in a new tab)
CWE-73  (opens in a new tab)

How to fix?

Upgrade Minimos:latest atlantis-fips to version 0.45.0-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream atlantis-fips package and not the atlantis-fips package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

Atlantis is a self-hosted golang application that listens for Terraform pull request events via webhooks. From 0.19.8 until 0.45.0, Atlantis does not consistently validate user-controlled workspace values supplied through accepted repository-level atlantis.yaml configuration or authenticated /api/plan input before joining them into local workspace paths. Traversal segments can escape the intended per-pull workspace directory and cause clone preparation or other working-directory code paths to call os.RemoveAll, os.MkdirAll, or related filesystem operations on out-of-bounds directories before Terraform rejects the invalid workspace name. This can create, delete, or reuse writable paths with the privileges of the Atlantis process, causing integrity loss or denial of service. This issue is fixed in version 0.45.0.