GitBook Breach Exposed Customer Data, Including Sign-In Docs
By Christine James, Editor · November 16, 2026
GitBook says an attacker reached its production systems on November 2, 2026 and could see customer data while inside, including documentation sites that sit behind sign-in. In its security notice, GitBook says it has "treated all customer data as exposed, not only the targeted customer." Service came back on November 3 after about 16 hours offline.
What Happened
GitBook says the attacker used a stolen key to get production secrets, which gave full infrastructure access through a service account. The company disabled the affected accounts within hours, which stopped the attack and took the app offline.
The attacker had access for about 2 hours 45 minutes on the evening of November 2 and about 40 minutes early on November 3. GitBook says the activity appears aimed at one customer, but the access covered everyone's data.
The disclosure is also listed in the Software Security Incidents 2026 tracker.
What Was Exposed
GitBook lists the customer data the attacker could reach during that window:
- GitBook API tokens
- Integration tokens and secrets
- Session signing secrets
- Questions site visitors asked GitBook Assistant
- Documentation sites using sign-in (authenticated access)
- Connected GitHub and GitLab repositories, where the attacker could act as the GitBook app in repositories customers had shared
- Customer content such as docs, spaces and change requests
GitBook says it found no evidence that any other customer's content was modified, and it cannot tell whether the attacker took action in customer repositories. Billing details, passwords and IP addresses were not compromised.
What GitBook Did
While offline, GitBook rotated every production secret and every customer secret it manages, invalidated API tokens issued before its cutoff and rebuilt its servers. It also disabled its back office while it added safeguards, and apologized for not telling customers sooner.
What Customers Should Do Now
- API users: create a new API token and update any apps that use the old one.
- Connected tools: rotate third-party tokens or secrets used with GitBook.
- Published integrations: rotate the secrets they use.
- Sign-in docs with a custom backend: regenerate the signing key and update your backend.
- GitHub and GitLab: GitBook rotated these keys, but review recent activity in repositories you shared with it.
GitBook also published the attacker's IP addresses in its notice, so teams can search their own logs.
For alternatives and what buyers pay, see the GitBook page.
Review GitBook or share what you pay.
Sources
GitBook on HissingKitty
No bills yet
What teams pay
No ratings yet
Ratings
4
Alternatives listed
Built Something Like This?
List it free, or tell other teams what you pay today.

