Git credentials are exposed in Atlantis logs

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

8.5 · 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 · score source

EPSS

• CVE-2024-52009: 0.72% estimated exploitation activity in the next 30 days; percentile 53.91 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary Short summary of the problem. Make the impact and severity as clear as possible. For example: An unsafe deserialization vulnerability allows any unauthenticated user to execute arbitrary code on the server. Atlantis logs contains GitHub credentials (tokens ghs...) when they are rotated. This enables an attacker able to read these logs to impersonate Atlantis application and to perform actions on GitHub. When Atlantis is used to administer a GitHub organization, this enables getting administration privileges on the organization. This was reported in https://github.com/runatlantis/atlantis/issues/4060 and fixed in https://github.com/runatlantis/atlantis/pull/4667 . The fix was included in Atlantis v0.30.0. Details Give all details on the vulnerability. Pointing to the incriminated source code is very helpful for the maintainer. While auditing the Kubernetes/Argo CD/Atlantis deployment of some company, the following set-up was encountered: - Most employees have read-only access…

Published by the source

8 Nov 2024, 19:03 UTC

Last modified by the source

26 Jun 2026, 19:29 UTC

Source last checked

26 Oct 2026, 15:24 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-gppm-hq3p-h4rp

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-52009

Advisory: Git credentials are exposed in Atlantis logs
IDs: CVE-2024-52009, GHSA-gppm-hq3p-h4rp
Record: https://patchnext.com/advisories/cve-2024-52009 (revision 1, source checked 26 Oct 2026, 15:24 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/runatlantis/atlantis 0.30.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/runatlantis/atlantis: affected < 0.30.0; fixed in 0.30.0

## Suggested inspection (read-only)
- Go github.com/runatlantis/atlantis: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/runatlantis/atlantis.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-gppm-hq3p-h4rp (GitHub-reviewed advisory GHSA-gppm-hq3p-h4rp lists affected ranges: Go github.com/runatlantis/atlantis >=0 <0.30.0)

Commands are suggestions: review each one before running it.