NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules, #400 by repository stars
Latest stable
v0.50.0
Last release today
22 Nov 2026
Ships on a steady schedule
a new release about every 8 days
Some releases are documented
notes for 27 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
9 years old
1630 releases · first in 2017
Drag across the ruler to compare, or tap a release to open it.
Nothing published for this version
Docker image: Alpine OpenSSH 10.3_p1-r2 for CVE-2026-123158 ( #7065 ), Alpine curl 8.23.0-r0 ( #7027 ), Alpine Git 2.54.1-r0 ( #7093 ), Alpine base 3.…
v0.50.0 fixes one high-severity security advisory and is a breaking release for anyone using the API or drift detection, which now require an explicit experiment opt-in.
experiments setting before upgrading (see below). Without them, Atlantis refuses to start if api-secret or a drift flag is set, and /api/* routes return HTTP 404.team_authz.command users on Bitbucket Server or Azure DevOps: upgrade promptly (GHSA-7v86-958w-j7hj). No configuration change is needed.When team_authz.command is set in the server-side repo config, Atlantis built the external command as one string and ran it with sh -c. The repository full name was not quoted. On Bitbucket Server (project display name) and Azure DevOps (organization, project and repository names), a crafted name could run arbitrary commands on the Atlantis server with its environment and credentials, or make the check print pass and bypass the authorization decision.
The fix passes the Atlantis command name, the repository full name and each owner/team value as separate arguments, so the shell never parses them. The configured command and args are still run by sh, so commands that embed their own arguments keep working, and the argument order your script sees is unchanged.
team_authz.command configured, on Bitbucket Server or Azure DevOps. GitHub, GitLab, Gitea and Bitbucket Cloud repository names cannot contain shell metacharacters.args shift their positions.Reported by EZO Labs Security (@superbot-helper).
10.3_p1-r2 for CVE-2026-123158 (#7065), Alpine curl 8.23.0-r0 (#7027), Alpine Git 2.54.1-r0 (#7093), Alpine base 3.24.4 (#7076, #7104), git-lfs 3.8.1 (#7080).golang.org/x/crypto v0.59.0 (#7087), golang.org/x/net v0.62.0 (#7044), github.com/klauspost/compress v1.20.2 (#7066).minimatch 11 and overrides for vulnerable docs-site dependencies (#7045, #7021).The API (/api/plan, /api/apply, /api/locks) and drift detection are experimental features, and a new experiments server setting now has to grant each one:
api permits the command and lock routes.drift-detection permits the drift routes.What changes on upgrade:
api-secret, enable-drift-detection or enable-drift-remediation is set without the matching experiment.GET /api/locks, which used to be public.To keep your current behavior, add the experiments you use:
atlantis server --experiments=api,drift-detection
# or
ATLANTIS_EXPERIMENTS=api,drift-detectionexperiments:
- api
- drift-detectionFor a drift-only installation, use only drift-detection. Before rolling back to v0.49.0 or earlier, remove the experiments setting, because older binaries don't recognize it. See Experiments for details.
plan and apply, still go through the normal checks. To do this, Atlantis now looks up its own account identity on each VCS, including Bitbucket Server and Azure DevOps, and the GitHub App slug through the /app endpoint.atlantis-tests repo now run one at a time (#7097), and e2e runs clean up webhooks left by cancelled runs (#7103).Full Changelog: v0.49.0...v0.50.0
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
v0.47.1 fixed a shell-injection vulnerability ( GHSA-rjh2-4xgw-p2hj ) and changed behavior along the way, but its release notes didn't call that a bre…
v0.49.0 is a breaking release, for three reasons:
Every behavior change is also documented, in a Behavior change note, on the docs page where you would look for that setting. Read Breaking changes before you upgrade.
--default-tf-version (and --default-tf-distribution opentofu if you use OpenTofu) so Atlantis downloads the binary. If downloads are blocked, mount or copy a binary into the image instead. The image no longer ships one.--gh-hostname matches the host in your repositories' clone URLs. Webhooks whose clone URL is on a different host are now rejected.allow_custom_workflows: true together with allowed_workflows, check that every project's workflow is in the allow-list. Repo configs that used to pass can now be rejected.dir is a symlink to somewhere outside the repository.-out, -generate-config-out, -state, -state-out and -backup are now blocked after --, and that --blocked-extra-args can no longer unblock anything.-var-file: the allowlist now applies to apply, import and state rm as well as plan. Paths containing .. are refused, and so are repo symlinks that point outside the repository and the allowlist.state rm: if state is in --allow-commands, state rm now has to meet the project's apply_requirements and import_requirements.--api-secret is set, send X-Atlantis-Token on GET /api/locks. Check that /api/plan and /api/apply callers send clean, repo-relative paths[].directory values with no leading / and no globs.apply_requirements: [approved] now uses each reviewer's latest review. On Gitea, dismissed and stale approvals no longer count, and any push that changes the diff makes approvals stale.plan and apply is rejected and has to be re-planned.The Docker images no longer include Terraform or OpenTofu
latest, vX.Y.Z and vX.Y.Z-debian images no longer bundle Terraform or OpenTofu binaries, and they set no default Terraform version. This was announced in the v0.48.0 release notes. The -alpine-slim and -debian-slim images from v0.48.0 were the intermediate step toward this and are no longer published. If you pinned one, switch to the unsuffixed, -alpine or -debian tag, which now contain the same thing. If you build the image yourself, use --target alpine or --target debian; the -slim targets are gone.terraform or tofu binary on PATH, or on the version the image used to set by default.terraform not found in $PATH. Set --default-tf-version ....--default-tf-version (ATLANTIS_DEFAULT_TF_VERSION, or Helm defaultTFVersion) so Atlantis downloads that version at startup. Repos can still pin their own version with terraform_version.--default-tf-distribution opentofu (Helm defaultTFDistribution).PATH yourself: mount one, or build FROM ghcr.io/runatlantis/atlantis and copy one in. Set --tf-download=false so Atlantis uses it and doesn't try to download.v0.47.1 fixed a shell-injection vulnerability (GHSA-rjh2-4xgw-p2hj) and changed behavior along the way, but its release notes didn't call that a breaking change. If you are upgrading from v0.47.0 or earlier, these apply to you.
Terraform and conftest commands no longer run through a shell
sh -c. Commands now run as argument vectors.
extra_args entry is passed as exactly one argument. Shell operators (;, &&, |, redirections), globbing and word splitting no longer apply.$WORKSPACE and $DIR are still expanded in operator-configured extra_args, but no longer in arguments typed in a PR comment after --.path and each extra_args entry are still split on whitespace. Quote a path that contains a space.extra_args relied on shell behavior, for example two flags in one entry, a pipe, a redirection or a glob.$VAR references in comment arguments and expected them to expand.run step, which still runs with a shell by design.Workspace names are validated everywhere
atlantis.yaml, the -w comment flag, the Terraform Cloud workspace read from HCL, and the API are validated. A name can't contain /, \, .., $, whitespace or control characters, can't be ., and can't start with - or ~.$ never worked, because the shell expanded it.workspace key, or the comment is rejected with the offending value and a reason such as cannot contain '/' or '\'.allowed_workflows is now checked for every project (GHSA-56q6-8vmp-v2qm)
allow_custom_workflows: true, a bug stopped the allowed_workflows check at the first project that used a repo-local workflow. Projects after that one were never checked. Now every project is checked.allow_custom_workflows: true, allowed_overrides: [workflow] and a non-empty allowed_workflows, whose atlantis.yaml has a later project naming a server-side workflow that is not in allowed_workflows.workflow '<name>' is not allowed for this repo.allowed_workflows in the server-side config, or change the project to use an allowed workflow.A project dir that symlinks outside the repository is rejected (GHSA-9q39-mgw7-5789)
dir (or a parent directory in its path) is a symlink pointing outside the clone. That includes absolute targets and ../ targets that leave the repository. Symlinks that stay inside the repository (for example dir -> modules/x) still work.project path traversal detected: .... A path that cannot be resolved for any other reason (for example a file where a directory is expected) now fails with resolving project path: .... Before, Atlantis ignored that case.dir symlink keeps the existing dir "<dir>" does not exist error. If anything other than a regular file (for example a symlink) sits at the plan file path inside the project directory, Atlantis deletes it before planning.More Terraform flags are blocked after --, and --blocked-extra-args now adds to the list instead of replacing it (GHSA-chm7-fjpm-927x)
-chdir, -plugin-dir, -out, -generate-config-out, -state, -state-out, -backup. Before, only -chdir and -plugin-dir were blocked.- and -- spellings and the =value form.--blocked-extra-args now adds to the built-in list. Before, setting it replaced the defaults, so an operator could unblock -chdir or -plugin-dir that way. That is no longer possible.atlantis plan -- -generate-config-out=..., which some teams use to generate config for import blocks.--blocked-extra-args to allow one of the default flags.-state or -backup to atlantis state rm in comments. Those are blocked too.flag "<arg>" is not allowed in extra args.-generate-config-out or the other flags, put them in extra_args of a workflow you control (server-side, or a repo workflow the server allows). Workflow extra_args are not checked.--blocked-extra-args, you can drop the -- entries. Nothing breaks if you leave them.The comment -var-file allowlist covers more commands, spellings and paths (GHSA-chm7-fjpm-927x)
--var-file-allowlist (default: --data-dir) is now enforced on apply, import and state rm, not only plan.--var-file and values that contain =... element is refused, even if it would resolve inside the repository (for example envs/../common.tfvars).-var-file in comment extra args is checked. Workflow extra_args are not.-var-file in comments on these commands with a path outside the repository and the allowlist, a path containing .., or a path that goes through a committed symlink leading outside the repository.var file path <p> is not allowed by the current allowlist: [...]var file path <p> must not contain '..' elementsvar file path <p> resolves to <r>, which is not allowed by the current allowlist: [...]var file path <p> is a symbolic link whose target does not exist--var-file-allowlist.atlantis state rm now enforces apply and import requirements (GHSA-cxvq-66x3-pwhw)
state rm used to skip command requirements entirely. It now has to meet every requirement in the project's apply_requirements plus every one in its import_requirements. There is no separate state_rm_requirements key.state in --allow-commands and projects that set apply_requirements or import_requirements (approved, mergeable, undiverged, policies_passed).state rm is refused with the usual requirement messages, ending in before running state. For example: Pull request must be approved according to the project's approval rules before running state.state rm, or loosen the requirements for that project. If Atlantis can't fetch the PR status, approved and mergeable count as not met.GET /api/locks requires X-Atlantis-Token when an API secret is set (GHSA-xgrg-fpp6-q6fm)
--api-secret set. Web basic auth never covered /api/ paths.GET /api/locks without a token on servers that have --api-secret set. If no API secret is set, the endpoint stays open.UNAUTHORIZED and message invalid or missing API token. The 401 body uses the newer API error envelope, not the old top-level lock-list body.X-Atlantis-Token: <api secret>.paths[].directory is validated on /api/plan and /api/apply (GHSA-mwfx-fvfc-7q5w)
What changed: non-empty directories have to be clean, repo-relative paths. The request is now rejected for:
/.. that leaves the repository* ? [ ] { }Valid values are cleaned: ./dir and dir/ both become dir. An empty directory is still allowed.
Who is affected: API callers that send any of these. Before v0.49.0:
/modules/vpc ran in modules/vpc but didn't match that directory's atlantis.yaml project, so it ran with default project settings./ meant the repo root.envs/* matched configured projects by pattern. The API docs already said globs were unsupported, but the code accepted them. That undocumented behavior is gone.How to tell: HTTP 400 with invalid directory "<dir>": directory must be a clean repo-relative path.
What to do: send directories relative to the repo root, with no leading slash. Use . for the repo root. List each project directory explicitly instead of using a glob.
GitHub clone URLs must be on the configured GitHub host, and head and base repos must share a host (GHSA-6mjf-4m52-m5cq)
--gh-hostname (default github.com). The check runs on webhooks, on API plan/apply requests, and when a comment command fetches the pull from GitHub. The comparison ignores case and port. A clone URL with no host is rejected.--gh-hostname is not the host GitHub puts in clone URLs. For example: an internal alias or IP address, or a reverse-proxy name that differs from the GHES hostname.parsing pull data: ... expected clone url host "<gh-hostname>" but had "<host>". Check your webhook deliveries in GitHub for 400s after upgrading.failed to parse repository: ..., and comment commands fail with the same host error.head repo host "<x>" does not match base repo host "<y>", not running command at warn level.--gh-hostname to the hostname that appears in your repositories' clone URLs.Approval checks use each reviewer's latest review (GitHub, Gitea) (GHSA-fm5f-jg8p-x2vw)
apply_requirements: [approved] (and import_requirements / state rm), Atlantis now reads every page of reviews and takes each reviewer's most recent approve or request-changes review.
approved. On Gitea, any push that changes the diff invalidates every existing approval until reviewers approve again.Pull request must be approved according to the project's approval rules before running apply. even though an old approval is visible on the PR.Apply is refused when the plan file differs from the one recorded at plan time (GHSA-5vwh-xc92-8h64)
plan step, Atlantis records a SHA-256 of the plan file with the project's plan status.apply rejects a plan file that no longer matches that hash, and deletes the file.plan step leaves no plan file now fails at plan time instead of at apply.run steps in the plan stage can still post-process the file.run steps record no hash and are not checked. Plans recorded before the upgrade carry no hash and are still accepted.pre_workflow_hooks or tooling that rewrite or replace the plan file between atlantis plan and atlantis apply. Workflows whose plan stage includes plan but somehow don't leave the plan file at the expected path.plan file for dir "<d>" workspace "<w>" project "<p>" does not match the plan that was recorded when it was created; run `atlantis plan` .plan step did not write a plan file for dir "<d>" workspace "<w>" project "<p>".atlantis plan again. Don't modify the plan file after the plan stage finishes. Any post-processing has to happen inside the plan stage, before Atlantis records the hash.PlanHash is a new field in stored project status and in PlanSuccess API responses. Old stored data decodes unchanged.GitHub App setup flow is bound to the browser that started it (GHSA-rx6x-hrg2-g435)
/github-app/setup now issues a one-time state nonce and an HttpOnly cookie, both valid for 10 minutes. /github-app/exchange-code only accepts a callback that carries both.Atlantis already has GitHub credentials) in the same process. Before, that only happened after a restart with credentials configured, so record the credentials shown before leaving the page.GitHub app setup state is not valid for this browser, start again from /github-app/setup or GitHub app setup state expired, start again from /github-app/setup.--web-basic-auth while setting up.output: hide on custom run and multienv steps now also hides output when the step fails, in both the PR comment and the job message. The multienv parse error no longer echoes the offending line; it now reads like invalid environment variable definition: misquoted at offset 8. env steps are unchanged.| Advisory | Severity | Summary | Reported by |
|---|---|---|---|
| GHSA-6mjf-4m52-m5cq | Critical | Clone URL host was not checked against the configured VCS host, so the fork check could be bypassed and untrusted code run. | @watsa01 |
| GHSA-56q6-8vmp-v2qm | High | A later project in a multi-project atlantis.yaml could skip the server's allowed_workflows check. |
@bcarikci-dev |
| GHSA-5vwh-xc92-8h64 | High | Apply did not bind to the reviewed plan, so a replaced plan file could be applied under an existing approval. | @luantq0 |
| GHSA-9q39-mgw7-5789 | High | A symlink in a pull request could make Terraform run, or write its plan file, outside the checkout. | @zer0d4y5, @Hama1cco, @avrlab233, @manus-use |
| GHSA-fm5f-jg8p-x2vw | High | Dismissed Gitea approvals (and superseded GitHub approvals) still met apply_requirements: [approved]. |
@danieltk76 |
| GHSA-mwfx-fvfc-7q5w | High | /api/plan and /api/apply did not validate paths[].directory at the API boundary. (The authentication half was fixed in v0.45.0; constant-time basic auth is GHSA-48vm.) |
@SnailSploit |
| GHSA-xgrg-fpp6-q6fm | High | GET /api/locks exposed lock metadata without an API token. |
@SDSZEHTZ, @hatjwe |
| GHSA-48vm-qqx3-7w83 | High | Web basic auth credentials were compared in non-constant time. | @iaohkut-from-NightWolf-Team |
| GHSA-chm7-fjpm-927x | Medium | The comment -var-file allowlist could be bypassed, allowing arbitrary file reads on the Atlantis server. |
@dashingDragon, @arpitjain099, @kah-ja, @luantq0, @dead1nfluence |
| GHSA-cxvq-66x3-pwhw | Medium | atlantis state rm ignored apply and import requirements. |
@luantq0 |
| GHSA-jxcj-v552-f5q4 | Medium | output: hide on custom run and multienv steps leaked output into PR comments when the step failed. |
@bcarikci-dev |
| GHSA-rx6x-hrg2-g435 | Low | The GitHub App setup callback had no CSRF protection (state parameter). |
@geo-chen |
Thank you to everyone who reported these issues, and to @chenrui333 and @pseudomorph for reviewing every fix.
parallel_plan is honored for API plans and drift detection (#6963).Full Changelog: v0.48.2...v0.49.0
Emergency security release for the eMudhra intermediate CA key compromise . The private keys of eight eMudhra (emSign) intermediate certificates were…
Emergency security release for the eMudhra intermediate CA key compromise. The private keys of eight eMudhra (emSign) intermediate certificates were compromised; some of those intermediates are cross-signed by a root that every trust store includes. We recommend all users upgrade.
crypto/x509 rejects any certificate chain containing the eight compromised keys (CVE-2026-111943). Go does not check revocation, so Atlantis v0.48.1 and earlier, built with go1.27.1, would accept a certificate issued with those keys for any host, including the VCS APIs Atlantis sends credentials to. go1.27.3 also includes the standard library fixes from go1.27.2.ca-certificates is updated to Alpine 20261020-r0 and Debian 20250419+deb13u1. Both remove emSign ECC Root CA - G3, and Debian also removes the Comodo AAA Services root that cross-signed some of the affected intermediates. This covers the other TLS clients in the image (git, curl, Terraform/OpenTofu and conftest).8.14.1-2+deb13u7 and openssl 3.5.7-1~deb13u3 security pins, Alpine 3.24.2, Terraform 1.16.5, conftest 0.70.1.golang.org/x/net v0.60.0 and vite v8.3.3.If you build Atlantis yourself, rebuild with go1.27.3 or go1.26.10 or later. The terraform, tofu and conftest binaries are built by their own projects; update them when their releases with the Go fix are available.
Full Changelog: v0.48.1...v0.48.2
fix: anchor the prefix when a repo allowlist rule has a mid-string wildcard ( GHSA-fwc4-2f3p-7qm7 ) by @jamengual in #6962
Full Changelog: v0.48.0...v0.48.1
Thanks to @arpitjain099 for reporting and reviewing this fix, and to @pseudomorph for reviewing.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.