Hundreds of Leaked GitHub App Keys Still Grant Access, Some With Organization Admin Rights

GitGuardian found 474 of 4,802 publicly exposed GitHub App private keys still authenticate, some enabling repository access and full organization takeover because such keys never expire unless manually revoked.

GitGuardian analyzed 4,802 publicly exposed RSA private keys paired with GitHub App IDs, collected since 2019, and found 474 (roughly 10 percent) still authenticated as 440 distinct Apps. GitHub App private keys do not expire until manually deleted, and a holder can mint access tokens indistinguishable from the App itself. About 72 percent of the valid keys could read private repository content, 207 could write to it, 98 could control workflows, 40 could administer self-hosted runners, and 44 held organization-administration rights capable of enabling organization takeover. One App for Access Tokens for GitHub Actions, whose key was exposed in January 2024, was installed on roughly 300 organizations, including Civica and Sierra Nevada Corp. Named affected parties included the CDC, BuildBuddy, and Crusher.dev: a CDC App key leaked in a CDCGov repository in April 2025 was revoked on September 18, 2025 after disclosure, BuildBuddy and the Actions maintainer also rotated keys and reported no malicious use, and a Crusher.dev key from 2020 reportedly still works on an unmaintained project.