Skip to main content
VulnerabilityPublished

CVE-2026-116676: runatlantis atlantis · OS Command Injection

Affects runatlantis atlantisSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High : upgrade to 0.47.1 soon.

Data as of 27 Oct 2026, 17:43 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 0.47.1
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade atlantis and github.com/runatlantis/atlantis to 0.47.1.

Affected software

ProductAffectedFixed in
runatlantisatlantisAffected
  • >=0.4.0 <0.47.1
Fixed in
  • 0.47.1
Gogithub.com/runatlantis/atlantispkg:golang/github.com/runatlantis/atlantisOther threatsAffected
  • >=0.4.0 <0.47.1
Fixed in
  • 0.47.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Atlantis to version 0.47.1 or later, where this vulnerability is fixed. Until then, restrict pull request contributors and carefully manage the --allow-fork-prs option to limit exposure. No other mitigations are specified by the vendor advisory.

Description

CVE-2026-116676 is a command injection vulnerability in Atlantis, a self-hosted Golang application for Terraform pull request automation. Versions from 0.4.0 up to but not including 0.47.1 allow authenticated contributors to inject arbitrary shell commands via the workspace name in atlantis.yaml. This occurs because the workspace value is passed unsafely to a shell command executed with sh -c. Exploitation can lead to arbitrary command execution with the privileges of the Atlantis service account, exposing sensitive credentials and resources. The issue is fixed in version 0.47.1.

References

Community reviews

Loading reviews…