Sso
Security incidents tagged Sso. Newest first.
1 Sso incident in the last 12 months
- Incidents
- 1
- Live
- 1
- Patched
- 0
- Days without an incident
- 0
- Longest quiet run: 0 days
Sponsored
Brought to you byTinkerer Club
The private club for people who own their servers, run their own AI, and pay $0/month for software.
- HighPartly patched
GitBook breach: SSO flaw led to production access; all API tokens revoked, rotate integration secrets
On Nov 2 2026 an attacker used a flaw in GitBook's SSO login flow to create sessions as GitBook staff, pulled credentials for a misconfigured internal GitHub App to reach GitBook's code repositories and a Cloudflare API key, and from there reached production secrets with full infrastructure access. GitBook took its app offline for about 16 hours (20:32 UTC Nov 2 to 11:56 UTC Nov 3), rotated every infrastructure and GitBook-managed customer secret, and invalidated all API tokens. It says the attack targeted one customer, but treats all customer data as exposed: API tokens, integration tokens and secrets, session signing secrets, authenticated-access docs, content, and the ability to act as the GitBook GitHub and GitLab apps in repositories customers had granted. GitBook says it can't tell whether the attacker acted in customer repositories. Billing data and passwords were not affected. Customers should create new API tokens, rotate third-party and integration secrets, regenerate authenticated-access signing keys, re-authenticate the GitBook MCP server, review connected repositories, and check logs for the published IPs.
GitBook (hosted documentation platform)Since Nov 2, 2026
