← Qubole

2026 Qubole — AWS cross-account access; customer clouds

2026 Unknown records affected Share on X

Data compromised

In observed victim AWS accounts: S3 objects the integration role could read, plus credentials taken from Lambda environment variables, Secrets Manager and SSM Parameter Store. Some discovered keys were tested against AWS, Entra ID and Okta. No public unique-people census. recordsAffected 0. Which Qubole customers were reached is unpublished.

Technical writeup

Indexed from the 9 Nov 2026 Wiz CIRT post. companyConfirmed stays false until Qubole or Idera publishes a notice. Do not treat unused IAM roles as proof that every Qubole customer was copied.

Root cause

Wiz, working with Sentra and Mandiant, observed an actor using IAM credentials from an AWS account associated with Qubole between 14 and 26 October 2026. The actor assumed customer IAM roles that trusted that vendor account, then enumerated resources, read secrets, and copied S3 objects. A separate burst of customer-owned Qubole integration keys ran 8-11 October. Qubole had not published a matching customer notice on pages reviewed 9 November. Researcher report, not a company 8-K.

References