← All stories
● Covered by 1 source · 1 reportMedium impact1 negative

Rackspace Spot Breach Exposes Customer Kubernetes Secrets and Allows Unauthorized Workloads

🔄 Updated 1h ago
New to BrevFeed? We gather this story from every outlet covering it into one summary — ranked by real-world impact, not just the latest headline — so you never miss what matters. What is BrevFeed? →

Key points

  • Attackers accessed Rackspace Spot on November 17, 2026, using leaked credentials.
  • Unauthorized parties deployed workloads and read Kubernetes Secrets in customer clusters.
  • Rackspace revoked tokens, removed pods, and strengthened access controls.
  • Customers must re-issue API tokens, rotate credentials, and check logs.

Breach Details and Timeline

Rackspace informed customers about a breach in its Rackspace Spot cloud platform. Attackers gained access to parts of the platform on November 17, 2026, between approximately 00:20 and 22:00 UTC, using leaked credentials. Rackspace learned of the intrusion on November 18 after a customer report and confirmed the impact on the same day.

Impact on Customer Kubernetes Clusters

The unauthorized access allowed attackers to act as legitimate users within some customer organizations. This enabled them to create pods in Kubernetes clusters, read Kubernetes Secrets, and list nodes and volumes. Kubernetes Secrets store sensitive information such as passwords, authentication tokens, and API keys, meaning attackers could have read any Secret stored in an affected user's clusters, as well as any Spot API tokens or refresh tokens.

Rackspace's Remediation Actions

In response to the breach, Rackspace revoked affected tokens and sessions, removed the unauthorized pods, rotated keys, and strengthened access controls and monitoring. The company also provided indicators of compromise, including specific IP addresses and suspicious Kubernetes pod prefixes.

Customer Actions Required

Affected customers have been instructed to take several steps to secure their environments. These include reissuing their Spot API tokens, replacing refresh tokens used in automation tools, downloading fresh Kubernetes configuration files, and rotating credentials stored in their cluster Secrets. Additionally, customers were advised to analyze logs from November 17 onwards for databases, container registries, Git repositories, cloud storage, and third-party services to identify any potential misuse of exposed credentials.

✨ This summary was generated by AI from the outlets' reporting listed below. It is not independently verified and may contain errors — check the original sources. How BrevFeed works →

The daily brief

One email each morning: the day's tech stories, clustered across outlets and summarized. No account needed.

One email a day. Unsubscribe in one click, any time.

Today's brief

Spend a few minutes, get the whole day. Every topic's top stories in one hands-free rundown — listen, watch, or read the transcript.

~4 min · 3 stories · Nov 21

▶ Play today's brief Listen on Spotify

New every morning, and the back catalogue is archived by date.

Reporting from

Rackspace disclosed a security breach in its Rackspace Spot cloud platform where attackers used compromised credentials to access customer Kubernetes clusters. The intrusion allowed unauthorized workload deployment and access to sensitive Kubernetes Secrets, including passwords and API keys. Rackspace has revoked tokens, removed unauthorized pods, and advised affected customers to rotate credentials and analyze logs for potential abuse.