Skip to content
Brief Security & Trust ·

Rackspace says leaked logins let attackers into Spot customers' Kubernetes secrets

Attackers used leaked credentials on 17 November and could read stored Secrets in some customer clusters.

In brief
  • Rackspace said an outsider used leaked credentials to reach parts of Rackspace Spot on 17 November 2026. In some customer accounts, the intruder could read Kubernetes Secrets.
  • The Spot console outage temporarily kept customers from rotating credentials. Rackspace said service was fully restored on 21 November after multiple delays.

BleepingComputer reported on 21 November that Rackspace warned customers of a break-in at Rackspace Spot, its Kubernetes cloud service. Rackspace said an outsider used leaked credentials on 17 November, between about 00:20 and 22:00 UTC. It learned of this on 18 November from a customer report. In some customer organizations, the intruder could act as a real user: start pods (small units of running software), read Secrets, and list nodes and volumes.

Rackspace said the intruder could have read any Secret in an affected user's clusters, plus that user's Spot API and refresh tokens. It said it revoked tokens, removed the rogue pods and rotated keys. BleepingComputer got no reply on how many customers were hit or whether data was stolen. The Spot console outage temporarily kept customers from rotating credentials. Platform9 co-founder Sirish Raghuram said on Reddit that access was shut on purpose while the environment was sanitized. Rackspace said service was fully restored on 21 November after multiple delays.

Here the platform login was the real boundary. Rackspace says acting as a user was enough to read Secrets, which hold passwords and keys for databases and cloud services. Fixing it also needed the console, which was off for a time. Buyers can ask how they would rotate keys if a provider's console went down.

A WebPulse Brief: a short report of an important event, written by the WebPulse Newsroom with AI assistance and checked against the reporting below. When there is more to explain, we follow up with a full story. How we use AI.

Reporting: BleepingComputer.