security —

Rackspace Spot breach lets hackers access Kubernetes secrets, causes admin console outage

Rackspace notified clients that compromised credentials enabled unauthorized deployment of workloads and access to Kubernetes secrets within customer clusters on its Rackspace Spot cloud platform.

Rackspace Spot breach lets hackers access Kubernetes secrets, causes admin console outage

The platform, which facilitates deployment and management of containerized applications utilizing Kubernetes, experienced the intrusion. The disclosure, obtained by BleepingComputer, indicated that attackers accessed platform components on November 17, 2026, between roughly 00:20 and 22:00 UTC.

Rackspace learned of the intrusion on November 18 following a report from a customer, confirming that the recipient organization was impacted that same day. The notification stated, "On 17 November 2026 (about 00:20–22:00 UTC), an unauthorized party used leaked credentials to access parts of Rackspace Spot."

Attackers gained the capability to operate as legitimate users in certain customer organizations, permitting the creation of pods in Kubernetes clusters, reading Kubernetes Secrets, and listing nodes and volumes.

Kubernetes Secrets house sensitive data such as API keys, authentication tokens, and passwords needed to access various systems, including cloud services and databases. Rackspace cautioned that the attackers might have viewed any Secret stored in an affected user's clusters, alongside any Spot API or refresh tokens belonging to that user.

The provider stated it has taken remedial actions, including revoking sessions and tokens, eliminating unauthorized pods, strengthening monitoring, and rotating keys. Affected customers were directed to reissue Spot API tokens, replace automation tool refresh tokens, download new Kubernetes configuration files, and rotate credentials stored in cluster Secrets.

Market participants were also advised to examine logs from November 17 onward across databases, cloud storage, Git repositories, container registries, and third-party services to detect potential misuse of exposed credentials.

Sirish Raghuram, co-founder and Chief Growth Officer of Platform9, which co-developed Rackspace Spot, commented on the situation. He stated, "I've been instrumental in creating Spot and in its operations to date, and I can tell you that the team and I are incredibly disappointed to have let you down in this way," adding, "I know you disagree, but we made the decision that shutting all access down and sanitizing the entire environment is what we can do to best protect everyone using Spot."

This incident resulted in a prolonged outage of the Rackspace Spot administration console, temporarily impeding customer cluster management and the rotation of potentially compromised credentials. Service was fully reinstated by Rackspace on November 21.

The occurrence highlights ongoing operational risks associated with credential management within managed container orchestration environments, necessitating rigorous security posture maintenance by platform operators.

Why it matters

This incident highlights critical supply chain risks within cloud infrastructure, where compromised credentials can grant deep access to sensitive container orchestration secrets. Operators must immediately review their access controls and credential rotation policies to prevent similar platform-level compromises.

Earlier coverage

securitycloud

Related coverage

Elsewhere in this edition