← All resources

GitBook: All personal API tokens revoked after November 2 breach

First reported 2026-11-03 · security-incident · data-breach · confirmed

GitBook revoked all personal API tokens after a November 2 breach and urged customers to rotate secrets.

Data breach · Confirmed · First reported 3 Nov 2026 · Happened 2 Nov 2026

What has been reported

  • Where it happened: GitBook
  • Data reported as exposed: keys and secrets
  • Reach into customers: a source says the attackers may be able to reach GitBook's customers, through remote access, customer credentials or tokens, or software updates

How sure is this?

GitBook itself or an authority has confirmed the incident, according to the sources below.

Sources

  1. GitBook Revokes All Personal API Tokens After Breach (google.com, press, 3 Nov 2026)
  2. Unraveling the GitBook Breach and the Surge of AI-Enabled Cyber Threats (google.com, press, 5 Nov 2026)

Are you impacted?

If GitBook is one of your suppliers, ask it what was accessed and whether your data or your access was involved. Map your vendors in Resiliate to see incidents like this against your own supplier list and to record your answer.


Security incidents on Resiliate are in beta. This page is built from public reports and is updated when new sources appear; it was last updated on 22 Nov 2026. Something wrong? Write to hello@resiliate.io.