Security Digest · Nov 3, 2026 · Breach · Cloud

GitBook Breach: SSO Flaw Exposed Tokens and Repo Access

GitBook treats all customer data as exposed after a Nov 2 SSO flaw reached production. Replace API tokens and integration secrets, and review linked repos.

Our verdict

Act now

If your team uses GitBook, rotate every connected secret today and review repositories linked through Git Sync for November 2-3, because GitBook treats all customer data as exposed and cannot say whether the attacker acted in customer repositories.

Who must act: Every GitBook customer with API tokens, connected third-party tools, published integrations, authenticated documentation, the MCP server, or Git Sync to GitHub or GitLab.

Who can relax: Teams that do not use GitBook; readers of GitBook-hosted public documentation have nothing to rotate, and GitBook says billing data and passwords were not compromised.

Affected
GitBook API tokens, integration tokens and integration secrets
Session signing secrets and documentation sites using authenticated access
Questions asked of GitBook Assistant by site visitors
Customer content: docs, spaces and change requests
GitHub repositories granted to the GitBook app and GitLab projects granted to GitBook (attacker could act as the integration)
Fixed in
SSO flaw fixed Nov 2, 2026, 19:58 UTC
All existing API tokens invalidated from Nov 3, 2026, 02:34 UTC
GitHub App keys rotated Nov 3, 2026, 10:52 UTC
All production secrets rotated Nov 3, 2026, 11:56 UTC
GitLab tokens for Git Sync rotated Nov 3, 2026, 22:51 UTC
CVSS
Not scored
EPSS
n/a
CISA KEV
Not listed
Exploitation
Exploited in the wild
Severity
Critical

What to do

  1. Create new GitBook API tokens and update every script, CI job and application that uses one.
  2. Rotate at the issuing provider any third-party token or secret connected to GitBook, and rotate secrets used by published integrations.
  3. Regenerate the signing key in GitBook if you use authenticated access with a custom backend, then update that backend.
  4. Re-authenticate the GitBook MCP server in every client that uses it.
  5. Review commits, pull requests, webhooks and deploy keys on repositories linked to GitBook for Nov 2-3, 2026.
  6. Search your logs for the three IP addresses GitBook published.
  7. Check that your published documentation still contains the commands, links and addresses you expect.

How to check if you are affected or compromised

  • Search your environments for 94.183.188.91, 45.139.84.195 and 198.251.83.217, as GitBook recommends.
  • On repositories linked through Git Sync, list changes from Nov 2-3, 2026 with git log --since=2026-11-02 --until=2026-11-04 --all, and investigate anything nobody on your team made.
  • Review GitHub or GitLab audit logs for activity by the GitBook integration during Nov 2-3, 2026, especially new webhooks, deploy keys or workflow changes.
  • Check any service reached with a token stored in GitBook for use you cannot explain since Nov 2, 2026.

What happened#

On November 3, 2026, GitBook, a widely used platform for product and developer documentation, disclosed a breach in its security incident post. A flaw in its SSO login flow let an attacker create sessions acting as GitBook staff. From there, the attacker queried the authentication details of a misconfigured GitHub App integration, reached internal code repositories, and eventually found a Cloudflare API key. That key led to production secrets and full infrastructure access through a service account.

In GitBook's timeline (UTC), the first account at the targeted customer was hijacked at 12:27 on November 2. The attacker reached staff sessions and source code at 16:32 and production at 17:48. An internal alert fired at 18:10, the SSO flaw was fixed at 19:58, and GitBook cut the attacker off and took the app offline at 20:32. All secrets were rotated and the service was back by 11:56 on November 3, after about 16 hours of downtime. GitBook puts the attacker's access at about 2 hours 45 minutes that evening and about 40 minutes early on November 3.

GitBook says the attack was aimed at one customer, which it has not named: "Everything we've seen points to an attack aimed at one GitBook customer rather than at GitBook as a whole." It describes "a sophisticated, highly targeted attack using AI agents," and says the attacker "moved with a speed and precision that pointed to an attack driven largely by automation and AI." Decrypt notes that GitBook has not said which AI systems were used. Nothing in the disclosure ties the intrusion to GitBook's own AI products.

Who is affected#

All customers. Although the activity centered on one customer, GitBook treats all customer data as exposed. The attacker could reach:

  • GitBook API tokens, integration tokens and secrets, and session signing secrets
  • documentation sites using authenticated access, and customer content such as docs, spaces and change requests
  • questions visitors asked GitBook Assistant
  • internal source code, infrastructure secrets, database credentials and Git Sync secrets

The attacker could also act as the GitBook app in GitHub repositories customers had granted it, and could temporarily act on GitBook's behalf in granted GitLab projects. GitBook says billing information, passwords and IP addresses were not compromised, and that it found no evidence other customers' content was modified.

Crypto projects stand out because many publish user instructions on GitBook. Decrypt reports that PancakeSwap took its docs offline and moved them to its own infrastructure, while saying they were not compromised.

Do you really need to act?#

Yes, if you use GitBook, even though you are probably not the target. GitBook has already revoked API tokens and rotated the secrets it manages, so the old GitBook credentials should no longer work. That does not cover secrets you issued elsewhere and connected to GitBook. Those stay valid until you rotate them at the source.

The bigger question is your code. GitBook is direct about this: "We cannot determine whether they took any action in customer repositories." It says no action is needed for Git Sync keys because it rotated them, and it does not ask customers to review their repositories. We recommend reviewing anyway, because GitHub App credentials with write access can change code.

If your documentation tells users what to install or where to send funds, check that too. Altered instructions are a direct route to your users.

What to do now#

  1. Create new GitBook API tokens and update every script, CI job and app that used the old ones.
  2. Rotate third-party tokens and secrets connected to GitBook at their issuing provider, and rotate secrets used by published integrations.
  3. If you use authenticated access with a custom backend, regenerate the signing key in GitBook and update the backend.
  4. Re-authenticate the GitBook MCP server in each client.
  5. Review each linked repository for November 2-3 with git log --since=2026-11-02 --until=2026-11-04 --all --format='%h %an %ae %s'.
  6. Check the same repositories for webhooks, deploy keys and workflow files you did not add. With the GitHub CLI: gh api repos/OWNER/REPO/hooks and gh api repos/OWNER/REPO/keys.
  7. Compare published docs with what your team wrote, especially install commands, download links and wallet or contract addresses.

How to tell if you were hit#

  • GitBook recommends searching your environments for three IP addresses: 94.183.188.91, 45.139.84.195 and 198.251.83.217.
  • In GitHub or GitLab audit logs, look for activity by the GitBook integration on November 2-3 that does not match a real documentation sync.
  • Check every service reached by a token stored in GitBook for activity since November 2 that you cannot explain.

GitBook says it will contact affected customers directly if further findings change the picture. A clean result lowers the risk but cannot rule out access, since the company itself cannot say what happened in customer repositories. Early coverage of the first notice reflects a narrower scope than the later post-mortem, so rely on GitBook's current page.

Timeline#

  • — 12:27 UTC, first hijacked account at the targeted customer. 17:48, attacker reaches production. 18:10, internal alert. 19:58, SSO flaw fixed. 20:32, attacker cut off and app taken offline.
  • — 02:34 UTC, existing API tokens invalidated. 10:52, GitHub App keys rotated. 11:56, all secrets rotated and service restored. GitBook publishes its first notice at 13:15 CET. 22:51 UTC, GitLab tokens rotated.

Sources

Original sources first: vendor and project advisories, CVE and government records, the discoverers’ write-ups. Every claim above links to one of these. See how the Security Desk works.

Original and primary sources

  1. GitBook — Security incident, November 2026 (updates and post-mortem) gitbook.com
  2. Decrypt — Crypto docs host GitBook hit by AI agent security breach, urges users to rotate keys decrypt.co
  3. Let's Data Science — GitBook discloses AI agent attack, tells customers to rotate tokens letsdatascience.com