GITHUB-ACTIONS · AUGUST 2026 · EARLY WARNING

Atlantis Path Traversal Vulnerability: Upgrade to 0.45.0

EARLY WARNING · UNCONFIRMED. This page describes a developing threat that 0Day surfaced from early signals and has not yet independently confirmed. Details may change. Always verify against the primary sources before acting.
Severity
HIGH
Affected component
atlantis (github-actions)
Patched version
0.45.0
GHSA-26W5-6G95-GJ28

Atlantis versions 0.19.8 to 0.45.0 have a path traversal vulnerability that allows out-of-bounds directory deletion and creation. Upgrade to Atlantis 0.45.0 or later to mitigate the risk.

What happened

Atlantis versions 0.19.8 to 0.45.0 reportedly have a path traversal vulnerability in workspace handling. This vulnerability allows out-of-bounds directory deletion and creation. The issue is fixed in Atlantis 0.45.0. To assess your exposure, check if you are using an affected version of Atlantis. If so, you are potentially vulnerable to this path traversal attack.

The vulnerability was first flagged on 2026-08-21T20:55:33+00:00. It is tracked under GHSA-26W5-6G95-GJ28. The vulnerability has not been exploited in the wild as of the latest reports. However, it is recommended to upgrade to the patched version as soon as possible to mitigate any potential risk.

What to do about it

How 0Day would have caught this

MATCHED TO YOUR ACTUAL DEPENDENCY GRAPH0Day matches every incoming threat signal against your GitHub organization’s full dependency graph, including transitive dependencies. If atlantis is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.

Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.

Frequently asked questions

Am I affected?

If you are using Atlantis version 0.19.8 to 0.45.0, you are affected by this vulnerability.

What should I do right now?

Upgrade to Atlantis 0.45.0 or later to mitigate the path traversal vulnerability.

Has this been exploited in the wild?

No, the vulnerability has not been exploited in the wild as of the latest reports.

Sources

Join the 0Day waitlist →

← Back to all threats