Qubole: cross-account access abuse

Qubole

Threat actor used IAM credentials from Qubole's AWS account to assume integration roles in customer AWS environments

Do this now

Check Qubole's advisory for a fix, and restrict access to the integration roles in your AWS accounts meanwhile.

First seen: 9 Nov 2026
Last update: 9 Nov 2026, 18:17 UTC
Source: news

Check this repository for exposure to one security incident from pwned.coffee. Report first, change nothing until I say so.

## Qubole: cross-account access abuse
Severity: unknown. Patch status: fix status unknown.
Affected: Qubole

Threat actor used IAM credentials from Qubole's AWS account to assume integration roles in customer AWS environments

## Steps
1. Search the repo, its CI and infra config for Qubole. If present, report the version in use and whether it's affected.
2. No source names a fix yet; check the vendor advisory. Until one ships: restrict network access to it.

## Report
A table: file, product or package, version in use, affected yes/no, exact fix. Then anything a human has to check outside the repo.

If you have the pwned.coffee MCP server (https://pwned.coffee/mcp), call lookup_cve for the latest, and check_repo with this repo's lockfiles, Dockerfiles and workflows for a full receipt.
Sources: https://www.wiz.io/blog/qubole-cross-account-access-abused-in-the-wild https://thehackernews.com/2026/11/hackers-exploit-quboles-trusted-aws.html
https://pwned.coffee/i/qubole-cross-account-access-abuse

Timeline

9 Nov 2026, 18:17 UTC
Reported by thehackernews.com: Hackers Exploit Qubole's Trusted AWS Access to Breach Customer Accounts and Steal Data
9 Nov 2026
First reported.

Receipt

Exploitation: No known exploitation
Score: No CVSS published yet: severity unknown.
Last checked: 13 Nov 2026, 16:26 UTC

Sources: KEV – CVE record – Vendor –

Sources

Follow on X

Totalone coffee