Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.1amended

Atlantis Workspace Handling has Path Traversal that Allows Out-of-Bounds Directory Deletion/Creation

CVE-2026-64679GHSA-26w5-6g95-gj28

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/runatlantis/atlantis 0.45.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.1 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
EPSS
  • CVE-2026-64679: 0.80% estimated exploitation activity in the next 30 days; percentile 56.54 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary Atlantis versions = 0.19.8 and < 0.45.0 did not consistently validate user-controlled workspace values before using them to construct local workspace paths. A crafted workspace value containing path traversal segments could cause Atlantis to resolve workspace paths outside the intended per-pull workspace directory. In vulnerable versions or code paths, Atlantis could create, use, or remove/recreate out-of-bounds directories with the privileges of the Atlantis process user, before Terraform rejected the invalid workspace name. The issue is fixed in Atlantis 0.45.0. Details The issue is a path traversal vulnerability in Atlantis workspace handling. workspace values can be supplied through repository-level atlantis.yaml configuration accepted by the server or through authenticated API input. A value such as ../../../../../../../../tmp/f1-canary could escape the intended Atlantis workspace root. In affected code paths, Atlantis used the resolved workspace path for local…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-26w5-6g95-gj28

  2. Revision 2 · amended ·

    Amended from osv record GO-2026-6273

  3. Revision 1 · created ·

    Published from osv record GHSA-26w5-6g95-gj28

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-64679

Advisory: Atlantis Workspace Handling has Path Traversal that Allows Out-of-Bounds Directory Deletion/Creation
IDs: CVE-2026-64679, GHSA-26w5-6g95-gj28
Record: https://patchnext.com/advisories/cve-2026-64679 (revision 3, source checked 26 Oct 2026, 15:28 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/runatlantis/atlantis 0.45.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/runatlantis/atlantis: affected >= 0.19.8, < 0.45.0; fixed in 0.45.0

## Suggested inspection (read-only)
- Go github.com/runatlantis/atlantis: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/runatlantis/atlantis.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-26w5-6g95-gj28 (OSV record GHSA-26w5-6g95-gj28 lists affected ranges: Go github.com/runatlantis/atlantis >=0.19.8 <0.45.0 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6273 (OSV record GO-2026-6273 lists affected ranges: Go github.com/runatlantis/atlantis >=0.19.8 <0.45.0 (fixed))
- Verified: https://github.com/advisories/GHSA-26w5-6g95-gj28 (GitHub-reviewed advisory GHSA-26w5-6g95-gj28 lists affected ranges: Go github.com/runatlantis/atlantis >=0.19.8 <0.45.0)

Commands are suggestions: review each one before running it.

Loading voting…