GitHub (2023): what the sources say about the cloud incident
Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.
GitHub disclosed the incident on 23 Mar 2023. What was exposed, as the sources state it: The company stated GitHub.com's RSA SSH private key was briefly exposed in a public GitHub repository; it stated it had no reason to believe the key was abused and that no GitHub systems or customer information were compromised.
Open the ledger · Report a correction
- Disclosed
- 23 Mar 2023
- Incident window
- not public
- Cloud or provider
- GitHub
- What was exposed
- The company stated GitHub.com's RSA SSH private key was briefly exposed in a public GitHub repository; it stated it had no reason to believe the key was abused and that no GitHub systems or customer information were compromised.
- How access was gained
- The company stated the exposure resulted from what it believes was an inadvertent publishing of private information.
- Access path
- Leaked access keys and secrets
- Kind of control that addresses it
- Run secret scanning on all repositories including private-to-public transitions, and keep host private keys in managed key storage
In the words of the source
“This week, we discovered that GitHub.com’s RSA SSH private key was briefly exposed in a public GitHub repository.” (company statement, We updated our RSA SSH host key)
Primary sources
- company statement: We updated our RSA SSH host key, dated 23 Mar 2023
If a field is wrong or a newer primary source exists, write to the editor with the entry name in the subject.
Related pages
Sources
- We updated our RSA SSH host key, read 16 Nov 2026
Last reviewed 16 Nov 2026.