Nullify

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.

Home
›
Incidents
›
GitBook Security Incident: What Happened and What to Rotate
App-layer breach
Adjacent

GitBook Security Incident: What Happened and What to Rotate

An attacker exploited a flaw in GitBook's SSO login flow on November 2, 2026, moved from forged staff sessions to production secrets, and GitBook treats all customer data as exposed.

Nullify Team
·
Disclosed
November 3, 2026
·
Updated
November 16, 2026

What happened in the GitBook security incident?

In its post-mortem, GitBook says an attacker exploited a flaw in its SSO login flow on November 2, 2026 to create sessions as GitBook staff. With those sessions, the attacker queried the authentication details of a misconfigured GitHub App in GitBook's organization, reached internal code repositories and obtained a Cloudflare API key that led to production secrets.

GitBook fixed the SSO flaw at 19:58 UTC on November 2, took the app offline, redeployed with new secrets and was fully back online at 11:56 UTC on November 3, after about 16 hours. It says the attack targeted one customer but treats all customer data as exposed.

What data was exposed in the GitBook breach?

  • GitBook API tokens, integration tokens and secrets, and session signing secrets.
  • Questions asked to GitBook Assistant, documentation sites using authenticated access, and customer content such as docs, spaces and change requests.
  • GitBook says billing information, passwords and IP addresses were not compromised, and it found no evidence other customers' content was modified.

How to check if you're affected

  1. List every GitBook API token, integration and published integration your team uses, and every site that uses authenticated access with a custom backend.
  2. Search your environments' logs for the three IP addresses GitBook published in the post-mortem.
  3. Review repository and organization audit logs from November 2 onward for actions by the GitBook app.

What to do now

  1. Create new GitBook API tokens. GitBook revoked existing personal tokens, so apps that use them need the new token.
  2. Rotate third-party tokens and secrets connected to GitBook, and secrets used by published integrations.
  3. Regenerate the signing key for authenticated access with a custom backend, and re-authenticate MCP server connections.
  4. No action is needed for Git Sync with GitHub or GitLab. GitBook rotated those keys itself.

What the GitBook chain means for your own app

The chain ran from one authentication flaw to forged staff sessions, then to an over-scoped app credential, then to production. The questions for your own stack are whether a forged or replayed session in your SSO flow could reach internal tools, and whether any app installation holds credentials broader than its job needs.

Where Nullify fits

How Nullify Covers This Class of Attack

Adjacent
Authentication Bypass

Nullify's code analysis looks for authentication and authorization failures, including privilege escalation and business-logic flaws, on every pull request, and the AI pentest agent tests authenticated REST and GraphQL API flows. This is about the same class of bug in your code, not the vendor's.

We can't speak to GitBook's code. Rotating your GitBook tokens is the immediate fix.

Frequently Asked Questions

What happened in the GitBook security incident?

On November 2, 2026, an attacker exploited a flaw in GitBook's SSO login flow to forge staff sessions, used a misconfigured GitHub App to reach internal repositories, and obtained a Cloudflare API key that led to production secrets.

Do I need to rotate my GitBook API token?

Yes. GitBook revoked existing personal API tokens, so create a new one and update any app that uses it. Also rotate third-party secrets connected to GitBook and regenerate custom-backend signing keys.

Was GitBook Git Sync affected?

GitBook rotated the GitHub and GitLab keys used for Git Sync itself, so no customer action is needed there. GitBook says it cannot determine whether the attacker acted in customer repositories the app could access.

Were GitBook passwords leaked?

GitBook says billing information, passwords and IP addresses were not compromised. Tokens, integration secrets, session signing secrets and customer content were accessible, so rotate those.

Update Log

  • Nov 16, 2026: page published from GitBook's UTC post-mortem timeline.

Check your own code for the bug behind this incident

Nullify's AI harness finds, proves and fixes the same class of vulnerability in your code and dependencies, and hands your team a merge-ready pull request.