Executive Summary
On November 17, 2026, attackers used leaked credentials to access Rackspace Spot, a Kubernetes-based cloud platform, over a nearly 22-hour window (00:20–22:00 UTC). Operating as legitimate users, the threat actors deployed unauthorized pods, read Kubernetes Secrets containing passwords, API keys, and authentication tokens, and enumerated nodes and volumes across affected customer clusters. Rackspace discovered the intrusion on November 18 following a customer report, subsequently revoking tokens, removing rogue pods, rotating keys, and hardening access controls. The breach triggered an extended outage of the Spot administration console, with full service restoration announced on November 21, 2026.
This incident underscores a widening pattern of credential-driven cloud-platform compromises, where a single set of leaked credentials can cascade into full cluster-level access. As Kubernetes adoption accelerates across enterprises, attackers are increasingly targeting secrets stores and orchestration-layer permissions, making identity hygiene and workload segmentation critical priorities for security teams in 2026 and beyond.
Why This Matters Now
Kubernetes Secrets exposure is reaching critical scale: leaked cloud credentials are now exploited within seconds of exposure, and attackers pivot rapidly from credential theft to full cluster enumeration. With regulatory bodies tightening cloud security mandates and multi-tenant Kubernetes platforms serving hundreds of organizations, a single compromised credential can produce a supply-chain-scale blast radius affecting every downstream service and customer.
Attack Path Analysis
Attackers obtained leaked Rackspace Spot credentials through an undisclosed prior compromise, then authenticated as legitimate users to the Rackspace Spot control plane on November 17, 2026. Using valid session tokens, they escalated to full Kubernetes cluster operator permissions, deployed unauthorized pods across customer namespaces, read Kubernetes Secrets containing passwords and API keys, and potentially exfiltrated sensitive credentials to an external IP (23.224.79.106), resulting in prolonged service disruption and exposure of customer workload secrets.
Kill Chain Progression
This analysis maps confirmed threat intelligence to the full cloud kill chain to show where defensive gaps would emerge as an attack progresses.
Initial Compromise
Description
Attackers used pre-compromised or leaked Rackspace Spot credentials to authenticate to the Spot platform API as valid users. The credential source is undisclosed but consistent with credential stuffing, prior phishing, or dark web acquisition of leaked tokens. No vulnerability exploit was confirmed; access was achieved via valid authentication.
MITRE ATT&CK® Techniques
Valid Accounts
Valid Accounts: Cloud Accounts
Unsecured Credentials: Container API
Container and Resource Discovery
Deploy Container
Unsecured Credentials
Data from Cloud Storage
Cloud Storage Object Discovery
Potential Compliance Exposure
Mapping incident impact across multiple compliance frameworks.
NIST SP 800-53 Rev. 5 – Account Management, Authenticator Management, and Least Privilege
Control ID: AC-2, IA-5, AC-6
CIS Controls v8 – Account Management, Access Control Management, Application Software Security
Control ID: Control 5, Control 6, Control 16
PCI DSS 4.0 – Restrict Access to System Components, Identify Users and Authenticate Access, Log and Monitor All Access
Control ID: Requirement 7, Requirement 8, Requirement 10
NYDFS 23 NYCRR 500 – Access Privileges, Multi-Factor Authentication, Incident Response Plan
Control ID: 500.07, 500.12, 500.16
DORA (EU Regulation 2022/2554) – ICT Security Policies, ICT Change Management, ICT-Related Incident Management
Control ID: Article 9, Article 10, Article 17
CISA Zero Trust Maturity Model 2.0 – Continuous Identity Validation and Workload Authorization
Control ID: Identity Pillar – Advanced, Application & Workload Pillar – Optimal
NIS2 Directive (EU 2022/2555) – Risk Management Measures, Incident Handling, Reporting Obligations
Control ID: Article 21(2)(a), Article 21(2)(b), Article 23
Sector Implications
Industry-specific impact of the vulnerabilities, including operational, regulatory, and cloud security risks.
Information Technology/IT
Kubernetes credential compromise via Rackspace Spot exposed pod secrets, API tokens, and cluster configs, requiring immediate Zero Trust Segmentation and Egress Security controls to prevent lateral movement and data exfiltration.
Computer/Network Security
Credential-based cloud platform breach exploiting Kubernetes secrets highlights critical gaps in namespace enforcement, multicloud visibility, and pod-level segmentation controls mapped to NIST.800-53.SC-39 and ZTMM.Applications.
Financial Services
Exposed Kubernetes Secrets containing API keys, authentication tokens, and database passwords create direct PCI.4.0.3.6.1 and NIST.800-53.AC-6 compliance risk for financial workloads hosted on compromised cloud infrastructure.
Health Care / Life Sciences
Healthcare organizations running containerized workloads on Rackspace Spot face HIPAA.164.308(a)(1) violations if exposed Kubernetes Secrets contained patient data credentials or third-party health system API authentication tokens.
Sources
- Rackspace Spot breach let hackers access customer Kubernetes secretshttps://www.bleepingcomputer.com/news/security/rackspace-spot-breach-let-hackers-access-customer-kubernetes-secrets/Verified
- Rackspace Spot Reddit Community - Service Fully Restoredhttps://www.reddit.com/r/rxt_spot/comments/1y22b0d/service_fully_restored/Verified
- Rackspace Spot Reddit Community - Spot Down Right Nowhttps://www.reddit.com/r/rxt_spot/comments/1xzrao7/rackspace_spot_down_right_now/Verified
- Rackspace Technology Official Security Advisories and Notificationshttps://www.rackspace.com/securityVerified
- CISA Known Exploited Vulnerabilities Cataloghttps://www.cisa.gov/known-exploited-vulnerabilities-catalogVerified
- Kubernetes Secrets Documentation - Security Considerationshttps://kubernetes.io/docs/concepts/configuration/secret/Verified
Frequently Asked Questions
Cloud Native Security Fabric Mitigations and ControlsCNSF
Based on the attack progression modeled above, these are the defensive controls that would constrain each stage.
Aviatrix Zero Trust CNSF is directly relevant to this incident because attackers exploited valid credentials to traverse a multi-tenant Kubernetes environment with minimal network-layer resistance. Had Zero Trust segmentation and controlled egress been enforced, the attacker's ability to move across customer namespaces and exfiltrate secrets to an external IP would likely have been substantially constrained.
Control: Cloud Native Security Fabric (CNSF)
Mitigation: Network-layer policy enforcement within the CNSF fabric could limit the reachability of an authenticated but anomalous session, reducing the scope of platform resources accessible from a potentially compromised identity even after a successful login.
Control: Zero Trust Segmentation
Mitigation: Zero Trust segmentation could reduce the privilege scope available to any single authenticated identity by enforcing workload-level isolation, making it less likely that a single compromised session could traverse namespace boundaries or access cluster-wide administrative APIs without additional validation.
Control: East-West Traffic Security
Mitigation: East-west traffic enforcement could significantly reduce the attacker's ability to traverse customer namespace boundaries and inject workloads across tenant clusters, as inter-namespace and inter-cluster traffic paths would likely require explicit policy authorization rather than being implicitly permitted.
Control: Multicloud Visibility & Control
Mitigation: Centralized multicloud visibility and traffic control could reduce the likelihood that unauthorized pods establish undetected outbound communication channels, as anomalous workload traffic patterns toward external IP ranges would likely be observable and constrainable through unified policy enforcement.
Control: Egress Security & Policy Enforcement
Mitigation: Egress policy enforcement could reduce the attacker's ability to transmit harvested Kubernetes Secrets and credential material to external infrastructure, as outbound cluster traffic destined for unrecognized or unapproved external IP addresses would likely be constrained or blocked by defined egress controls.
Had prior-stage controls constrained lateral movement and egress paths, the scope of exposed customer tenants would likely have been smaller, reducing the number of affected clusters and limiting how broadly harvested credentials could be leveraged for downstream compromise of databases, registries, and cloud services.
Impact at a Glance
Affected Business Functions
- Kubernetes Container Orchestration and Workload Management
- Cloud Infrastructure Administration and API Access
- Secrets and Credential Management (API keys, tokens, passwords)
- Continuous Integration and Continuous Deployment (CI/CD) Automation Pipelines
Estimated downtime: 4 days
Estimated loss: N/A
Attackers accessed Kubernetes Secrets stored within affected customer clusters, which may have included database passwords, authentication tokens, API keys for cloud services, container registry credentials, and Git repository access tokens. Additionally, Rackspace Spot API tokens and refresh tokens used in automation tooling were exposed. The unauthorized parties also had the ability to read, list, and interact with node and volume configurations. The full scope of downstream credential abuse against databases, cloud storage, container registries, and third-party services remains unconfirmed as of the date of disclosure. The breach affected an undisclosed number of customer organizations that used the Rackspace Spot managed Kubernetes platform.
Recommended Actions
Key Takeaways & Next Steps
- • Enforce Zero Trust Segmentation at the Kubernetes namespace level: Deploy namespace-level identity-based policy enforcement (AKF/Zero Trust Segmentation) to ensure that even authenticated Spot platform users cannot read Secrets or create pods outside their authorized namespace scope, directly blocking the privilege escalation and lateral movement observed in this breach.
- • Apply East-West Traffic Security between tenant clusters: Implement workload-to-workload segmentation controls to prevent an attacker operating within one customer's cluster context from pivoting to or interacting with adjacent customer namespaces or cluster nodes, containing the blast radius of compromised platform credentials.
- • Deploy Egress Security and Policy Enforcement on all Kubernetes cluster outbound traffic: Configure FQDN-based egress filtering and outbound traffic controls on cluster egress paths so that unauthorized pods (prefixes i1, glm-, probe) cannot establish C2 channels or exfiltrate Secrets to external IPs such as 23.224.79.106 without policy authorization.
- • Enable Multicloud Visibility and Control plane anomaly detection: Instrument Spot platform API activity with centralized traffic observability and anomaly detection to identify suspicious automation patterns — such as bulk Secret reads, rapid pod creation across namespaces, or repeated API calls from a single identity — triggering alerts before exfiltration completes.
- • Encrypt Secrets in transit using High Performance Encryption: Ensure all Kubernetes Secret data accessed via the Spot platform API traverses encrypted channels (IPsec/MACsec equivalent at the data path layer) so that even if pod-level C2 channels are established, intercepted Secret values remain protected against passive packet-level capture during exfiltration.



