November 6, 2026
- GitBook’s postmortem traces its production breach from SSO to GitHub and Cloudflare. The company says an SSO flaw, a misconfigured GitHub integration and a Cloudflare API key enabled production access. GitBook is treating all customer data as exposed and cannot determine whether the attacker acted inside connected customer repositories; customers should rotate GitBook tokens, integration secrets and custom-backend signing keys. GitBook (earlier coverage). · Cloud, Identity & Incident Response
in ARTEX Operator Consoles Expose Near-Autonomous Cybercrime