Rackspace Spot breach exposed access to Kubernetes Secrets

Rackspace says leaked credentials let an attacker access parts of Rackspace Spot, create pods and read Kubernetes Secrets in some customer clusters.

Reader ratingRate this article

Loading reader rating…

Privacy-conscious voting uses a signed random browser identifier and a short-lived network hash; the rating tables contain no raw IP-address column.

Reader ratings require JavaScript; the article remains fully readable without it.

Rackspace Spot breach exposed access to Kubernetes Secrets

Rackspace told affected customers that an unauthorized party used leaked credentials to access parts of Rackspace Spot on November 17. The access could let the attacker act as legitimate users in some customer organizations, create pods and read Kubernetes Secrets, according to the customer notice obtained by BleepingComputer.[1]

Security incident • Reporting cutoff: November 21, 2026 at 6:57 PM EST / 2026-11-21T23:57:29Z

The bottom line

Potential exposure extends beyond the Spot platform because Kubernetes Secrets can hold credentials for databases, repositories, cloud services and other systems.[1] Rackspace’s live status page currently says “Partially Degraded Service” and restricts new organization signups until November 25 while prioritizing capacity for existing customers.[3]

Verified facts

Access windowNovember 17, about 00:20–22:00 UTC.[1]
Exposure predicateRackspace said attackers could read any Secret in an affected user’s clusters, plus Spot API and refresh tokens held by that user.[1]
Current service signalThe live status page reports partial degradation; it also says existing customers can keep bidding and running workloads.[3]

What happened

Rackspace said it learned of the intrusion on November 18 after a customer report. The leaked credentials reportedly allowed the attacker to create Kubernetes pods, read Secrets and list nodes and volumes in some customer organizations.[1] Rackspace said it revoked affected tokens and sessions, removed unauthorized pods, rotated keys and strengthened access controls and monitoring.[1]

Restoration and the current status

A November 21 post by u/sirishkr in the Rackspace Spot community said service had been fully restored and apologized for the extended maintenance window.[2] That restoration statement does not mean every current status indicator is green: the status page later displayed “Partially Degraded Service” alongside the signup restriction.[3]

What affected customers should do

Follow the incident-specific steps Rackspace sent to affected customers. As reproduced by BleepingComputer, those steps include reissuing Spot API tokens, replacing refresh tokens used by automation, downloading fresh Kubernetes configuration files and rotating credentials stored in cluster Secrets.[1]

Rackspace also advised reviewing logs for databases, container registries, Git repositories, cloud storage and third-party services from November 17 onward for possible use of exposed credentials.[1]

What remains unknown

Rackspace had not publicly stated how many customers were affected or whether customer data was stolen when BleepingComputer published its report.[1]

The public materials reviewed here do not establish that every Rackspace Spot customer or every cluster was accessed. The exposure language applies to affected users and organizations.

Sources

  1. Rackspace Spot breach let hackers access customer Kubernetes secrets — BleepingComputer, November 21, 2026.
  2. Service fully restored — Rackspace Spot community post by u/sirishkr, November 21, 2026.
  3. Rackspace Spot Uptime — live status page, retrieved November 21, 2026 at 6:57 PM EST.

Update and correction note: This article distinguishes the November 21 restoration post from the later live partial-degradation signal. The IT Guys will update the article if Rackspace publishes additional scope or remediation details.