Bitrise takes its mobile CI/CD platform offline after unauthorised access to an internal system, says it has found no evidence customer data, secrets or source code were exposed, and begins a phased restore
Bitrise said on its status page at 20:44 UTC on 13 November 2026 (04:44 AWST 14 November) that it was responding to a security incident affecting some of Bitrise's internal secrets, detected within the previous hour, and that it had temporarily taken Bitrise offline as a precaution.
Bitrise said it had no confirmation that any customer data or source code was accessed and was investigating urgently. Out of an abundance of caution, it recommends rotating any Git and source-code access credentials connected to Bitrise. The status page lists the incident as SEV-1 for all users, affecting Builds (CI), Insights, Release Management, CodePush, Account Management and Cache.
Its latest update at the time of this desk check, posted 00:03 UTC on 14 November (08:03 AWST), said Bitrise was still investigating the incident causing the service to be unavailable. (source: Bitrise status page)
UPDATE 14 Nov 2026: In an update posted 01:26 UTC on 14 November (09:26 AWST), Bitrise said it detected suspicious activity in one of its internal cloud environments on 13 November 2026 at 11:32 EST (16:32 UTC; 00:32 AWST 14 November), that its initial investigation confirmed unauthorized access to an internal system which does not store or process customer data, that it immediately took all of its services offline as a precaution, and that it had found no evidence that customer data, secrets, or source code were exposed.
In its next update, posted 02:29 UTC (10:29 AWST), Bitrise said it had still found no evidence of such exposure, was beginning to restore services in a controlled, phased manner, and did not yet have an estimated time for full restoration. Bitrise now recommends that, once its services are restored, customers rotate all secrets, access tokens, and certificates stored in Bitrise. (source: Bitrise status page)
UPDATE 14 Nov 2026 (later): In its latest update, posted 11:53 UTC on 14 November (19:53 AWST), Bitrise said it was still making progress restoring the service, expected logins to app.bitrise.io to be restored soon, and was still working on a timeline for full restoration; it recommends that, once customers are able to sign in, they rotate all secrets, access tokens, and certificates stored in Bitrise. (source: Bitrise status page)
UPDATE (15 Nov 2026): In updates posted from 17:06 UTC on 14 November (01:06 AWST 15 November), Bitrise said it had brought app.bitrise.io back online in a limited safety mode, with most features still unavailable, so that customers can sign in to review workspace settings, connected Git accounts, secrets, certificates and tokens, and rotate or revoke anything connected to Bitrise as a precaution.
In an update posted 19:31 UTC on 14 November (03:31 AWST 15 November), Bitrise said that, as a precaution, it shut down and rotated all secrets used by the platform for signalling minutes after it saw an indication of a live attack on its internal system.
Its latest update at the time of this desk check, posted 04:27 UTC on 15 November (12:27 AWST), says full functionality is not expected to be restored before 15 November, that the services brought back are secure, and the incident is still listed as SEV-1 for all users. (source: Bitrise status page)
UPDATE (16 Nov 2026): In updates posted from 23:18 UTC on 15 November (07:18 AWST 16 November), Bitrise said Builds (CI) functionality was gradually being restored and workspaces with a paid subscription can start builds, and that full functionality is expected to be restored on Monday, 16 November.
Its latest update at the time of this desk check, posted 04:04 UTC on 16 November (12:04 AWST), says Builds (CI) and BuildHub functionality is gradually being restored, the services brought back are secure, most features are still expected to be unavailable, and known issues include code-signing file uploads for Apple and Android; Bitrise still suggests rotating secrets, certificates and tokens as a precaution, and the incident is still listed as SEV-1 for all users. (source: Bitrise status page)
UPDATE (17 Nov 2026): Bitrise's latest update at the time of this desk check, posted 20:11 UTC on 16 November (04:11 AWST 17 November), says Builds (CI), BuildHub, Release Management and CodePush, and Build Cache functionality is gradually being restored, Remote Dev Environments and Insights are still in progress, the investigation is ongoing and customers with identified impact are contacted directly; Bitrise still recommends rotating all secrets, access tokens and certificates stored in Bitrise, and the incident is still listed as SEV-1 for all users. (source: Bitrise status page)
- Product
- Bitrise mobile CI/CD platform (Builds, Insights, Release Management, CodePush, Account Management, Cache)
- Versions
- n/a — service-side security incident
- Exploited in Australia?
- unknown
- Patch to
- Bitrise advice: rotate any Git and source-code access credentials connected to Bitrise (13 Nov); once services are restored, rotate all secrets, access tokens, and certificates stored in Bitrise (14 Nov). CyberStack suggestion (our own, not Bitrise's): also review any other secrets stored in Bitrise workflows, such as signing keys and API tokens, and watch the status page for updates.
