GitBook infrastructure intrusion prompts API-token revocation and secret rotation
GitBook confirms infrastructure-credential intrusion. Integration tokens, Git Sync secrets, API tokens and visitors’ Assistant questions may have been accessed. Customer API tokens were invalidated; users must rotate connected secrets and re-authenticate MCP. App, API and published docs are back, with some degradation; investigation continues.
- Disclosed
- Nov 3, 2026
- Updated Nov 3, 2026
- Severity
- Septic Tank Blew
- No CVE: a breach, not a bug
- Splash zone
- GitBook customers using API tokens, integrations, Git Sync, Assistant or MCP
- GitBook · SaaS · credentials
- In the wild
- Yes
- GitBook confirms unauthorized access to infrastructure credentials.
What happened
GitBook says an attacker gained infrastructure credentials on November 2 at 19:00 CET (18:00 UTC). The company attributes the targeted attack to AI agents, but names no framework or actor and publishes no CVE, exploit details, indicators or affected-customer count. Confirmed platform access supports L4; access to the listed customer-data categories remains possible, not confirmed for every organization.
The November 3 16:21 CET notice supersedes the 13:15 CET “no action yet” position: rotate existing GitBook and connected third-party credentials, published-integration secrets, and re-authenticate MCP. GitBook says it blocked the attacker, closed the vulnerabilities and replaced its infrastructure credentials. It reports no evidence that customer content was modified, which does not rule out reads or future findings. App, API and published docs are available again with some degradation; a full postmortem is pending. No connection to WorkOS/ARTEX or other recent incidents is established.
Downstream documentation response: PancakeSwap’s November 3 original says its documentation is back online after migration off GitBook to infrastructure it controls, with existing links preserved. Its earlier original explicitly says its docs were not compromised and its app was unaffected; the takedown was precautionary. This does not establish an exchange breach, injected wallet drainer or customer losses, and does not replace GitBook’s credential-rotation instructions.
Crime-scene timeline
Nov 2, 18:00 UTC
Attacker accesses infrastructure credentials
The original notice gives 19:00 CET (18:00 UTC); GitBook says it detected the attack immediately and later took services offline as a precaution.
Nov 3, 12:15 UTC
Initial notice reports platform intrusion
The 13:15 CET notice says data impact is still being investigated and no customer action is yet required.
Nov 3, 15:21 UTC
New guidance requires credential rotation
The 16:21 CET update replaces the earlier no-action guidance, identifies possible exposure categories and reports services available again with some degradation.
Nov 3, 2026
PancakeSwap restores documentation on its own infrastructure
Its original update says existing links still work. The earlier precautionary notice says its docs were not compromised and its app was unaffected.
Who said what
We list each claim and who made it. Primary sources (the vendor, the researcher, the registry) are marked. Where reports disagree, we grade by the worst credible case.
- GitBook November 3 security incident noticePrimaryFull 13:15/16:21 CET updates: confirmed infrastructure access, possible token/secret/question exposure, token revocation, required rotations/MCP re-authentication, and incomplete service restoration.
- GitBook original status incident historyPrimaryTracks precautionary downtime, restored app/public content and remaining degradation. Displayed times lack an explicit timezone, so they are not converted into timeline timestamps.
- PancakeSwap original precautionary noticePrimaryFull public original read without login: docs not compromised, app unaffected; temporary precautionary takedown and no wallet-connection/token-approval requirement.
- PancakeSwap original docs-migration updatePrimaryFull public original read: docs back on controlled infrastructure, existing links work. Displayed publication time lacks timezone; date-only timeline.