status
Security incident
Tue, Nov 3, 2026, 16:21 CET
The GitBook app, the GitBook API, and published docs are available again. A few services may still be degraded as we finish restoring everything to full performance.
What happened
GitBook has been the target of a sophisticated, highly targeted attack using AI agents.
At 19:00 CET, November 2, the attacker gained unauthorized access to some of our infrastructure credentials. We detected the attack immediately and acted swiftly to block further impact.
To make sure our infrastructure was fully secure, we then took the GitBook app and authenticated docs sites offline. We kept publicly published content live for as long as possible, using cached data.
What we did immediately
Blocked the attacker and closed the vulnerabilities involved
Replaced every credential and secret across our infrastructure
Brought services back only once we were confident they were secure
Invalidated every customer’s API tokens on our platform
Your data
Our investigation shows that the attacker may have accessed the following:
Integrations tokens
Git Sync secrets
API tokens
Questions asked to GitBook Assistant by your site visitors
At this stage, we have found no evidence that any of your content in GitBook was modified.
What you need to do now
Rotate any existing GitBook API tokens. We revoked all personal API tokens during the incident.
Rotate any third-party API tokens or secrets you use to connect other tools to GitBook.
If you have published integrations that use secrets, rotate those secrets.
If you use the GitBook MCP server, re-authenticate it.
Please contact your GitBook organization’s admin to assist with this process.
What we are doing next
Monitoring the situation in case of further attacks.
Introducing further security measures to our platform.
Writing a full post mortem that will be published soon with more detailed information about the incident.
If you have any further questions, please reach out to your account manager or our support team. You can also check status.gitbook.com for updates
Thank you for your patience, and we apologize again for the disruption
The GitBook Team
Tue, Nov 3, 2026, 13:15 cet
Yesterday, November 2, we detected a security incident affecting GitBook’s infrastructure. We contained it quickly and, as a precaution, we’ve taken some services offline while we secure our systems. We apologize for the disruption this is causing, but your security is our number one priority.
This is a platform wide issue affecting a number of customers. We’re actively working on a fix and will have an update for you in the coming hours.
What happened: We detected and contained unauthorised access to parts of GitBook’s infrastructure.
Service status: Some services are temporarily offline as a precaution and will be restored once systems are confirmed secure.
Customer data: The investigation is ongoing. We will confirm whether any data was affected once the review is complete.
Action required: None at this time. We’ll share instructions on any steps you may need to take once services are restored.
Updates: Live updates are available at status.gitbook.com. We’ll share a full post-incident report once the investigation is complete.
If you have any questions, please reach out to our support team or contact your account manager
Thank you for bearing with us, we apologize again for the inconvenience.
The GitBook Team
FAQs
Is my data compromised?
Why are some GitBook services offline?
What are you doing to solve the problem?
Do I need to do anything right now?
Where can I get updates or ask questions?
