Rackspace Spot breach exposed customer Kubernetes secrets
Rackspace told customers attackers used leaked credentials to reach its Spot cloud platform on November 17 and read Kubernetes Secrets. Affected users must rotate tokens and every credential stored in their clusters.
By JetherVerse News

Rackspace warned customers on Friday, November 21, 2026 of a breach on its Rackspace Spot cloud platform. BleepingComputer reports the attackers used leaked credentials to reach parts of the platform on November 17, between about 00:20 and 22:00 UTC, and read Kubernetes Secrets in customer clusters.
Rackspace Spot lets organizations run containerized applications on Kubernetes. According to the notice sent to affected customers, the intruders acted as legitimate users in some customer organizations. They created pods, listed nodes and volumes, and read Kubernetes Secrets. These Secrets store passwords, authentication tokens and API keys for databases, cloud services and other systems. Rackspace says the attackers had access to any Secret in an affected user's clusters, along with Spot API tokens and refresh tokens held by the user.
Rackspace learned of the intrusion on November 18 after a customer report. The company says the team revoked affected tokens and sessions, removed the unauthorized pods, rotated keys and tightened access controls and monitoring. The breach also caused a long outage of the Spot administration console, which blocked customers from managing clusters and rotating credentials. Sirish Raghuram, co-founder of Platform9, which co-developed Spot, said on Reddit the team chose to shut down all access and sanitize the whole environment. Service returned in full on November 21 after several delays.
Affected customers must reissue Spot API tokens, replace refresh tokens in automation tools, download fresh Kubernetes configuration files and rotate every credential stored in cluster Secrets. Rackspace also urges teams to review logs for databases, container registries, Git repositories, cloud storage and third-party services going back to November 17. The company shared one IP address, 23.224.79.106, the range 23.224.0.0/15, and the pod and object prefixes i1, glm- and probe as indicators of compromise. Rackspace has not said how many customers were affected or whether data was stolen. BleepingComputer's request for comment went unanswered.
Why this matters: a stolen Secret works like a spare key. Rotating the lock after a breach closes the door, but only if every copy is replaced. If you run workloads on Rackspace Spot, treat each credential in your clusters as exposed until you replace the value, and check your logs for the listed indicators.
Read the full report at BleepingComputer.
Source: BleepingComputer
Get the news in your inbox
The tech stories that matter from JetherVerse News, with the source on every one.

