AI agent incident
GitBook says a targeted attack "using AI agents" reached its production infrastructure through an SSO flaw
What happened
GitBook, a documentation platform, said an attacker exploited a flaw in its SSO login flow on November 2 to act as GitBook staff, reached internal code repositories through a GitHub App, obtained a Cloudflare API key and then full infrastructure access through a service account. GitBook disabled the affected service accounts, which took the product offline for about 16 hours until 11:56 UTC on November 3. Exposed data includes API tokens, integration tokens and secrets, and session signing secrets. GitBook says the activity focused on a single customer and describes the attack as highly targeted and driven largely by automation and AI; it has not published evidence of the tooling.
Why it matters
Documentation platforms hold tokens into source repositories and, through their MCP servers, into agents. GitBook tells customers to issue new API tokens, rotate third-party and integration secrets, and re-authenticate the GitBook MCP server.
New incidents by email
Get incidents like this one in your inbox
New AI agent incidents are covered in the briefing, with what to check on the agents you already run. At least once a week, free.
You confirm by email. Unsubscribe in one click.
Sources
- gitbook.com GitBook security incident, November 3, 2026