# Bitrise: Incident updated: Security Incident

> Incident updated: Security Incident. Detected 2026-11-14 by Rewindex: what changed on Bitrise’s status page, with the before/after diff.

Canonical: https://rewindex.com/change/ra581c6253b80db
Last updated: 2026-11-14T02:33:38Z

**Summary:** _summary pending_
- Kind: Incident update · Label: not classified yet
- Changed: 2026-11-14 02:33 UTC · Detected: 2026-11-14 02:33 UTC
- [Source: https://status.bitrise.io/incidents/7055z4g9nbck](https://status.bitrise.io/incidents/7055z4g9nbck)
- [Company: Bitrise](https://rewindex.com/company/bitrise.md)
- Versions: before incident\_version:177/7055z4g9nbck@1e0809025d1b → after incident\_version:177/7055z4g9nbck@351dbb4ddee7
- Change 6 of 7 for this incident

## Discussed on Hacker News

- [Bitrise Suffers Security Incident](https://news.ycombinator.com/item?id=50489750): 3 points, 1 comments, posted 2026-11-13 21:13 UTC, posted 29 min after the vendor’s first update
- [Bitrise reports an active security incident](https://news.ycombinator.com/item?id=50490355): 1 points, 0 comments, posted 2026-11-13 21:48 UTC, posted 64 min after the vendor’s first update

Incident page (full timeline): [Security Incident](https://rewindex.com/company/bitrise/incidents/7055z4g9nbck.md)
## What changed

**1. Added: Update** (investigating) · 2026-11-14 02:29 UTC

```diff
+ After ongoing investigations we have still found no evidence that customer data, secrets, or source code were exposed. We are now beginning to restore services in a controlled, phased manner. We do not yet have an estimated time for full restoration. What we recommend As a precaution, once our services are restored, we recommend that you rotate all secrets, access tokens, and certificates stored in Bitrise. Services: All Services Scope: All Users Severity: SEV-1 When will the next update be available? You can expect a status update approximately 1 hour from now.
```

## History of this incident

| When (UTC) | Change | Label |
| --- | --- | --- |
| 2026-11-13 20:44 UTC | [Critical incident: Security Incident](https://rewindex.com/change/ia0acbba012a042.md) | critical |
| 2026-11-13 21:53 UTC | [Incident updated: Security Incident](https://rewindex.com/change/r445e00d56a966a.md) |  |
| 2026-11-13 23:03 UTC | [Incident updated: Security Incident](https://rewindex.com/change/ra8b289fb472052.md) |  |
| 2026-11-14 00:13 UTC | [Incident updated: Security Incident](https://rewindex.com/change/raec287d74a81ed.md) |  |
| 2026-11-14 01:33 UTC | [Incident updated: Security Incident](https://rewindex.com/change/rcd2b30cb973a39.md) |  |
| 2026-11-14 02:33 UTC | Incident updated: Security Incident (this change) |  |
| 2026-11-14 03:43 UTC | [Incident updated: Security Incident](https://rewindex.com/change/r6c7511c0059ed9.md) |  |

Previous: [change](https://rewindex.com/change/rcd2b30cb973a39.md) · Next: [change](https://rewindex.com/change/r6c7511c0059ed9.md) · All Bitrise changes: [timeline](https://rewindex.com/company/bitrise/changes.md)
_Diff excerpts are shown on normalized text: dates, counters and tokens appear as ‹date›, ‹count›, ‹tok›; noise-only edits are hidden. Rewindex shows the changed passages, not a copy of the page._

## Cite this

Incident updated: Security Incident on Bitrise’s status page, changed 2026-11-14 02:33 UTC (change 6 of 7).

- Canonical URL: https://rewindex.com/change/ra581c6253b80db
- Citation: Bitrise, “Incident updated: Security Incident” (2026-11-14 02:33 UTC). Archived by Rewindex: https://rewindex.com/change/ra581c6253b80db (CC BY 4.0).
- Markdown link: `[Bitrise: Incident updated: Security Incident (2026-11-14)](https://rewindex.com/change/ra581c6253b80db)`


---
Canonical: https://rewindex.com/change/ra581c6253b80db · Markdown: https://rewindex.com/change/ra581c6253b80db.md · JSON: https://rewindex.com/api/v1/changes/ra581c6253b80db · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-14T04:28:10.936Z