Rackspace Spot breach exposed customer Kubernetes secrets
Rackspace says an attacker used leaked credentials to access Spot on Nov 17, acting as legitimate users to read Kubernetes Secrets and Spot API tokens. Rotate everything now.
Rackspace says an unauthorized party used leaked credentials to access its Spot managed-Kubernetes platform on November 17, 2026, and, inside some customer organizations, could act as a legitimate user — enough to read Kubernetes Secrets. The disclosure comes from a notice Rackspace sent affected customers directly; it is not a public advisory. BleepingComputer obtained and reported the notice, and the account is corroborated by Mezha. Rackspace has not stated how many customers are affected or whether data was exfiltrated.
What happened
Per Rackspace's notice, the access window ran roughly 00:20 to 22:00 UTC on November 17. Rackspace learned of it on November 18 from a customer report. The attacker held leaked credentials that mapped to real user accounts in some tenant organizations. Operating as those users, they could:
- Create pods.
- Read Kubernetes Secrets — potentially any Secret in affected clusters.
- List nodes and volumes.
- Hold the affected users' Spot API tokens and automation refresh tokens.
Because a Kubernetes Secret commonly holds database passwords, cloud keys, registry credentials and TLS private keys, "read any Secret in the cluster" is the line that matters: treat every credential stored in an affected cluster as compromised until rotated.
Remediation and recovery
The platform was disrupted by an extended administration-console outage. Platform9 — which co-developed Spot — says access was deliberately shut down to sanitize the environment. Rackspace announced full restoration on November 21 after several delays.
Action checklist
Rackspace's notice to customers directs the following. If you run Spot, do all of it:
- Reissue your Spot API tokens.
- Replace any automation refresh tokens.
- Download new kubeconfig files.
- Rotate every credential stored in cluster Secrets — DB passwords, cloud keys, service-account tokens, registry creds, TLS keys.
- Review logs back to November 17 for unexpected pod creation, Secret reads, or node/volume enumeration tied to your user identities.
Context
This is a credential-abuse incident, not a product CVE: the attacker logged in as a real user, so there is no patch to apply — only rotation and audit. That is also why the blast radius is hard to bound from outside. The unanswered questions Rackspace has not addressed — how many tenants were in scope, and whether Secrets were copied rather than merely readable — decide whether this is a cleanup or a mass credential-rotation event across every downstream system those Secrets protected. Until Rackspace quantifies it, affected operators should assume the latter.