JupiteX Get the app
Science & Technology22 Nov 2026 · about 6 min

Rackspace Spot breach let hackers access customer Kubernetes secrets

The brief

The intruders did more than enter Rackspace Spot: in some customer organizations, they could act as legitimate users. That access mattered because it let them make changes and inspect information inside customer Kubernetes clusters. Rackspace said the attackers created unauthorized pods, read Kubernetes Secrets, and listed nodes and volumes. Secrets can hold passwords, authentication tokens, and API keys. The company warned that attackers could have read any Secret in affected users’ clusters, as well as their Spot API and refresh tokens. Rackspace says it revoked affected tokens and sessions, removed the unauthorized pods, rotated keys, and strengthened access controls and monitoring. Customers were told to reissue Spot API tokens, replace automation refresh tokens, download fresh Kubernetes configuration files, and rotate credentials in cluster Secrets. Rackspace did not say whether credentials were abused beyond Spot or whether customer data was stolen.

01

What did the attackers do after using leaked credentials to access Rackspace Spot?

The intruders did more than enter Rackspace Spot: in some customer organizations, they could act as legitimate users. That access mattered because it let them make changes and inspect information inside customer Kubernetes clusters.

Rackspace said the attackers created unauthorized pods, read Kubernetes Secrets, and listed nodes and volumes. Secrets can hold passwords, authentication tokens, and API keys. The company warned that attackers could have read any Secret in affected users’ clusters, as well as their Spot API and refresh tokens.

Rackspace says it revoked affected tokens and sessions, removed the unauthorized pods, rotated keys, and strengthened access controls and monitoring. Customers were told to reissue Spot API tokens, replace automation refresh tokens, download fresh Kubernetes configuration files, and rotate credentials in cluster Secrets. Rackspace did not say whether credentials were abused beyond Spot or whether customer data was stolen.

02

How long did the attackers have access, and how many customers are known to have been affected?

Rackspace placed the intrusion on November 17, 2026, from approximately 00:20 to 22:00 UTC. That window is about 21 hours and 40 minutes. It describes the period when the unauthorized party accessed parts of Rackspace Spot, according to the customer notification.

Rackspace said it learned of the intrusion the next day, after receiving a customer report. It confirmed that the reporting customer’s organization was affected on November 18. The company has not given a total number of affected customers in the information provided.

BleepingComputer asked Rackspace how many customers were affected and whether customer data was stolen, but had received no response. So the known details are the approximate access window and confirmation that at least the reporting organization was affected; the overall scale remains undisclosed. Rackspace instructed affected customers to rotate credentials and review service logs for possible misuse.

03

What are Kubernetes Secrets, and what kinds of information do they store?

Kubernetes Secrets are objects used to store sensitive information for applications and systems running in a Kubernetes cluster. The article names passwords, authentication tokens, and API keys as examples. These values matter because they can be used to authenticate to services, rather than being ordinary application data.

In the Rackspace Spot breach, attackers could read Kubernetes Secrets in affected users’ clusters. Rackspace warned that any Secret stored in those clusters could have been exposed. The company also said Spot API tokens and refresh tokens held by affected users could have been read.

A Secret’s contents may provide a route to other services, including databases, cloud services, and other systems, depending on what the credential is for. The article does not say that attackers used any exposed Secret outside the clusters or accessed those services. Rackspace told affected customers to rotate credentials stored in Secrets and examine logs for possible abuse.

04

What could attackers do with access to customer clusters and their Secrets?

The attackers’ compromised credentials let them act as legitimate users in some customer organizations. Rackspace said this access allowed them to interact with Kubernetes clusters, where organizations run containerized applications. The breach therefore exposed both cluster information and sensitive credentials stored within clusters.

Specifically, attackers could create pods, read Kubernetes Secrets, and list nodes and volumes. Rackspace warned that any Secret in an affected user’s clusters could have been read. Secrets may contain passwords, authentication tokens, or API keys, and the company said Spot API and refresh tokens could also have been exposed.

Those credentials can be used to access databases, cloud services, and other systems, so exposure could extend risk beyond the cluster. The article does not establish that attackers used credentials to enter those services or stole customer data. Rackspace revoked affected tokens and sessions, removed unauthorized pods, rotated keys, and asked customers to rotate credentials and review logs.

05

How can a password or API key stored in a cluster give attackers access to systems beyond that cluster?

A credential stored in a cluster can be more than a secret kept within that environment. The article explains that Kubernetes Secrets may hold passwords, authentication tokens, and API keys, which can be used to access databases, cloud services, and other systems. If an attacker reads a credential, it may provide a way to authenticate to the service that accepts it.

For example, if a Secret contains an API key used for a cloud service, someone who obtains that key could potentially use it to access that service. The same principle applies to a password or token for a database. The article does not describe a specific credential being used this way in the breach.

Rackspace warned customers to rotate credentials stored in their cluster Secrets and inspect logs for databases, container registries, Git repositories, cloud storage, and third-party services dating back to November 17. That advice was meant to help identify possible abuse; the company had not confirmed such activity in the information provided.

06

Why did Rackspace disable the Spot console, and how did that decision affect customers?

Rackspace Spot’s administration console suffered an extended outage after the breach. Sirish Raghuram, a Platform9 co-founder who helped develop Spot with Rackspace, said the team deliberately shut down access while securing the infrastructure. He said the decision to close access and sanitize the environment was intended to protect Spot users.

The shutdown had a practical cost for customers: they temporarily could not manage their clusters through the console or rotate credentials that might have been compromised. That made the outage especially difficult because customers had been told to replace API tokens, refresh tokens, configuration files, and credentials in Kubernetes Secrets.

After multiple delays, Rackspace announced that Spot service was fully restored on November 21. The company said it had revoked affected tokens and sessions, removed unauthorized pods, rotated keys, and strengthened access controls and monitoring. The article does not give further details about the delays or say how many customers were unable to use the console.

07

What is Kubernetes, and how does it help organizations run containerized applications?

The article describes Kubernetes as the technology organizations use through Rackspace Spot to deploy and manage containerized applications. A containerized application is packaged to run in a container, and Kubernetes helps manage those applications in clusters. This matters because a cluster can contain the workloads and configuration an organization relies on.

For example, a team can use Kubernetes to deploy an application and manage its running components. Rackspace said attackers in this incident could create pods and list nodes and volumes in affected clusters. In general Kubernetes usage, pods are units for running workloads, while nodes provide the cluster’s computing resources; these are general background details, not additional breach findings.

The incident shows why access controls around cluster management and stored credentials matter. Rackspace revoked affected tokens, removed unauthorized pods, and strengthened monitoring and access controls. It also asked customers to download fresh Kubernetes configuration files and rotate credentials stored in cluster Secrets.

This brief was written by AI from the original reporting and checked by other models. Names, figures and quotes come from the source; read it for full context.

Read more in the JupiteX app

Pulse is free. New stories every 4 hours, each one broken into the questions that explain it.

Or read more news on the web