2026-11-03
PingCAP (TiDB Cloud) Unauthorized Access and Data Leak (Up to About 50,000 Records in Japan): What TiDB Cloud Organization Admins Should Do About Account Data, SQL Editor History and Support Tickets
PingCAP says that between September 9 and October 7, 2026 (US time), an unauthorized party used stolen credentials to enter internal systems and copy data, and that up to about 50,000 personal records in Japan were found to have leaked (Japanese notice). The categories the company has confirmed as affected (varying by customer) are TiDB Cloud account data (user names, email addresses, organization and project associations, SQL editor execution history and errors, and inquiry information, meaning support tickets), business and billing information (names, emails, company names, phone numbers, orders, payment terms, billing settings) and the encrypted Public Key part of TiDB Cloud API keys. The company says it has not confirmed credit card leakage or unauthorized access to TiDB Cloud itself, and that Private Keys were not exposed. The unit the count measures (people or records) is not stated. The company's English notice also says source code was obtained. This site's conclusion: TiDB Cloud organization admins should rotate API keys, review access logs, members and roles, and change any credentials that may have been pasted into the SQL editor or a support ticket.