rewindex

ChangesBuildkiteBuildkite response to the eMudhra certificate compromise

Buildkite: Incident updated: Buildkite response to the eMudhra certificate compromise

Incident updateNormal progress (rule, 100%)Changed stspg.io (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

What changed

Struck in red is what Buildkite removed; blue is what they added. Muted text is unchanged context.

AddedUpdatemonitoring#1
Before: not present
After: We’ve finished updating the services that power Buildkite so they no longer trust the affected eMudhra certificates. No action is needed from customers for Buildkite hosted services. For components that run in customer infrastructure, we still recommend upgrading to the releases listed in our previous update (Buildkite agent v4.7.0 / v3.138.2, Buildkite CLI v3.64.2, and bktec v3.3.1). We’re continuing to release updates for the other binaries we distribute and will post them here as they ship.

Compared with the previous archived version of this incident (10 to 30-minute polling). View the live incident (opens in new tab).

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

History of this incident

Wednesday, October 21

2 incident changes

Tuesday, October 20

1 incident change

Cite this

Incident updated: Buildkite response to the eMudhra certificate compromise on Buildkite’s status page, changed 2026-10-21 05:13 UTC (change 2 of 3).

Title
Incident updated: Buildkite response to the eMudhra certificate compromise
Vendor
Buildkite
Date
URL
https://rewindex.com/change/r53532e500eac4e

All Buildkite changesBuildkite profileMarkdownJSON