SailPoint, Inc. (2026): what the sources say about the cloud incident
Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.
SailPoint, Inc. disclosed the incident on 8 May 2026. What was exposed, as the sources state it: A subset of the company’s GitHub repositories; the filing says no evidence that customer data in production or staging environments was accessed, and customers with information in the accessed repositories were notified.
Open the ledger · Report a correction
- Disclosed
- 8 May 2026
- Incident window
- detected April 20, 2026, as the filing says
- Cloud or provider
- GitHub
- What was exposed
- A subset of the company’s GitHub repositories; the filing says no evidence that customer data in production or staging environments was accessed, and customers with information in the accessed repositories were notified.
- How access was gained
- The filing says the company detected unauthorized access to a subset of its GitHub repositories and that the root cause was a vulnerability in a third-party application, which it does not name.
- Access path
- Third-party access
- Kind of control that addresses it
- review the scopes of every third-party application connected to source-control organizations, remove unused integrations, and patch or retire vulnerable ones
In the words of the source
“The root cause was a vulnerability in a third-party application, which has been remediated.” (regulator filing, SailPoint Form 8-K, Item 7.01, filed 2026-05-08)
Primary sources
- regulator filing: SailPoint Form 8-K, Item 7.01, filed 2026-05-08, dated 8 May 2026
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
- SailPoint Form 8-K, Item 7.01, filed 2026-05-08, read 16 Nov 2026
Last reviewed 16 Nov 2026.