CVE-2026-116676: Atlantis: OS command injection through PR-controlled Terraform workspace enables RCE during plan

Published Oct 27, 2026
·
Updated

Atlantis is a self-hosted golang application that listens for Terraform pull request events via webhooks. From version 0.4.0 until 0.47.1, Atlantis passes the pull-request-controlled workspace value from atlantis.yaml into Terraform command arguments that are joined with strings.Join(args, " ") and executed through sh -c. An authenticated contributor whose pull request is eligible for an Atlantis plan can include shell metacharacters in the workspace name, causing arbitrary commands to execute as the Atlantis service account without custom workflows, apply permission, or a malicious Terraform provider. External contributors can reach the flaw through fork pull requests only when --allow-fork-prs is enabled, while eligible same-repository branches do not require that option. The commands inherit the Atlantis process environment and can access cloud-provider, Terraform, and version-control credentials as well as files, state, and network resources available to the service. This issue is fixed in version 0.47.1.

Affected Software

1 affected component
Atlantis Atlantis>=0.4.0<0.47.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Atlantis to a version that resolves this vulnerability.

    Fixed in 0.47.1

Event History

Oct 27, 2026
CVE Published
via MITRE·05:11 PM
Data Sourced
via MITRE·05:11 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which contributors can exploit this issue?

Any authenticated contributor whose pull request is eligible for an Atlantis plan can exploit it from a same-repository branch. Contributors using fork pull requests can do so only if Atlantis is started with --allow-fork-prs enabled.

2

Is a custom workflow, apply access, or a malicious Terraform provider required?

No. Exploitation occurs during an Atlantis plan using a pull-request-controlled workspace value, and does not require custom workflows, apply permission, or a malicious provider.

3

What could an attacker access after successful exploitation?

Commands run as the Atlantis service account and inherit its process environment. They can access cloud-provider, Terraform, and version-control credentials, along with files, Terraform state, and network resources available to that account.

4

Which versions should be remediated?

Atlantis versions from 0.4.0 through 0.47.1 are affected according to the provided data. Update to the fixed version 0.47.1.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203