Rackspace Spot breach exposed customer Kubernetes secrets via leaked credentials
Rackspace has notified customers that an attacker used leaked credentials to access its Rackspace Spot Kubernetes platform on November 17, acting as legitimate users in some organizations. The intruder was able to deploy pods, read Kubernetes Secrets, and list nodes and volumes, potentially exposing passwords, tokens, and API keys stored in affected clusters. Rackspace detected the breach the next day after a customer report, revoked compromised tokens and sessions, removed unauthorized pods, and told affected customers to rotate credentials and reissue tokens.
GoKawiil's interpretation of the reporting above, not reported fact.
The breach shows how a single set of leaked credentials can cascade into broad access across multiple customer environments on a shared cloud platform, since Kubernetes Secrets often unlock databases, registries, and other downstream systems. Rackspace's advice to audit logs across databases, registries, Git repositories and cloud storage suggests the company cannot rule out that stolen secrets were already used elsewhere. The incident could prompt scrutiny of credential management practices on multi-tenant Kubernetes platforms more broadly.
- Attackers used leaked credentials to access Rackspace Spot on November 17, 2026, undetected for about a day.
- Intruders could read Kubernetes Secrets, deploy pods, and list nodes/volumes in affected customer clusters.
- Rackspace revoked tokens, removed unauthorized workloads, and urged customers to rotate all related credentials and audit connected services.
Source: bleepingcomputer.com, 2026-11-21
Published there as: “Rackspace Spot breach let hackers access customer Kubernetes secrets”
Read the original report → The summary and analysis above are GoKawiil's own, written from reporting by the source above. Facts and quotes belong to the original publisher.