← Back to context Comment by latchkey 12 days ago two days later... 2 comments latchkey Reply SamyPesse 12 days ago Sorry about that, I should have posted here. We posted a post mortem yesterday: https://www.gitbook.com/status/security-incident-2026-11-03 latchkey 12 days ago Thanks Samy."Using a flaw in GitBook’s SSO login flow, they were able to create login sessions acting as GitBook staff."Since this has now been closed, can we have more details on what happened?
SamyPesse 12 days ago Sorry about that, I should have posted here. We posted a post mortem yesterday: https://www.gitbook.com/status/security-incident-2026-11-03 latchkey 12 days ago Thanks Samy."Using a flaw in GitBook’s SSO login flow, they were able to create login sessions acting as GitBook staff."Since this has now been closed, can we have more details on what happened?
latchkey 12 days ago Thanks Samy."Using a flaw in GitBook’s SSO login flow, they were able to create login sessions acting as GitBook staff."Since this has now been closed, can we have more details on what happened?
Sorry about that, I should have posted here. We posted a post mortem yesterday: https://www.gitbook.com/status/security-incident-2026-11-03
Thanks Samy.
"Using a flaw in GitBook’s SSO login flow, they were able to create login sessions acting as GitBook staff."
Since this has now been closed, can we have more details on what happened?