Skip to main content
VulnerabilityPublished Updated

CVE-2024-52009: Atlantis logs · Git Credentials Are Exposed

Affects github.com/runatlantis/atlantisSource GCVE Database

0

Not known to be exploited · CVSS 8.5 High : upgrade to 0.30.0 soon.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 4.0 base score
8.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 53% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.30.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Nov 2024

  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 github.com/runatlantis/atlantis to 0.30.0.

Affected software

ProductAffectedFixed in
Gogithub.com/runatlantis/atlantisAffected
  • <0.30.0
Fixed in
  • 0.30.0

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.30.0 or later, where the logging of GitHub tokens during rotation has been fixed. Avoid granting unnecessary log read access to users. Patch status is confirmed fixed in Atlantis v0.30.0.

Description

Atlantis versions prior to 0.30.0 log GitHub tokens in plaintext during token rotation. This exposure in logs can allow unauthorized users with log access to impersonate the Atlantis application and perform privileged actions on GitHub organizations managed by Atlantis. The vulnerability was fixed in Atlantis v0.30.0.

References

Community reviews

Loading reviews…