GITBOOK · Vendor
NO FIX YET
GitBook, a hosted documentation platform, had a security incident affecting published sites and the GitBook app, now resolved. The sources say customer data was accessible to an attacker, but the text here does not list which data or how access was gained.
first public Nov 3, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
GitBook customers whose published sites or GitBook app accounts were affected; the sources point to a post-mortem at gitbook.com for which customer data was accessible, which the text here does not include. unknown
Not affected if no-gitbook-account
Who cares gitbook, security, self-hosted
Unknown from the sources.
No fix yet, per the sources.
As promised, now that the incident is resolved, we’ve published our full post-mortem on the recent security incident.
The post explains what happened, a full timeline, exactly which customer data was accessible, how we responded to protect our customers, and what we’re doing next.
We apologize again for the disruption. We hold ourselves to the highest standards, and we know an incident like this affects the trust you place in GitBook.
We hope the transparency in this post-mortem, our previous communications, and the actions we’ve taken help rebuild it.
If you have questions, contact your account manager or reply to this email to speak to our support team. For live updates, visit status.gitbook.com.
Sara Tandowsky, GitBook CEO Samy Pessé, GitBook Co-founder & CTO
This page as .md ·
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.