Loading story…
Palo Alto Networks Unit 42 reported a cross-account container takeover issue affecting Azure Container Instances (ACI), in which weaknesses in the service could allow one tenant to interfere with or gain control over containers belonging to another account. The finding raised concerns about tenant isolation in Microsoft’s serverless container platform, where customers rely on the cloud provider to enforce strict separation between workloads running on shared infrastructure.
The reported issue highlighted the risk that a compromise in ACI’s isolation model could expose customer applications, data, and credentials hosted inside affected containers. For defenders, the incident underscored the need to review cloud workload exposure in ACI, monitor for unauthorized container activity, and assess whether sensitive workloads should be segmented or moved until provider-side mitigations are confirmed.
See affected versions and whether adversaries are exploiting it.
1 event from the most recent confirmed update back to the earliest known activity.
Palo Alto Networks Unit 42 published research describing a cross-account container takeover issue affecting Azure Container Instances. The reference indicates public disclosure of the vulnerability but provides no additional event details such as patch timing or exploitation.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
1 reference tracked. Mallory keeps watching after this page renders.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Microsoft disclosed multiple vulnerabilities in **Azure Container Instances (ACI) Confidential Containers**, including **elevation of privilege** issues tracked as `CVE-2026-21522` and `CVE-2026-26124`, and an **information disclosure** flaw tracked as `CVE-2026-23655`. The advisories indicate security weaknesses affecting confidential container deployments, a technology intended to isolate sensitive workloads with stronger runtime protections. The disclosures come against a broader backdrop of container isolation concerns highlighted by **NVIDIAScape**, a vulnerability in the **NVIDIA Container Toolkit** tracked as `CVE-2025-23266`. Security researchers reported that the NVIDIA flaw could allow attackers to break container boundaries in AI and GPU-enabled environments, underscoring how weaknesses in container runtimes and supporting infrastructure can undermine assumptions about workload isolation even in hardened or confidential computing deployments.
Jul 12, 2026
Microsoft remediated a critical Azure Automation vulnerability, tracked as **`CVE-2025-29827`** and rated **CVSS 9.9**, that could have allowed an attacker to take over another tenant’s automation identity. The issue stemmed from a public-by-default Azure Automation configuration combined with additional code flaws, creating an exploit chain that let an attacker with access to their own Azure Automation account impersonate identities across tenants and potentially reach data, credentials, scripts, and other cloud resources. Reporting on the flaw said the attack path required three weaknesses: publicly exposed Azure Automation account endpoints by default and two separate code-level bugs. Microsoft said it changed the default behavior so Azure Automation identities are no longer public by default, and no known in-the-wild exploitation has been reported. The finding echoes earlier research into Azure Automation security and underscores how cloud identity exposure and chained logic flaws can turn default service settings into high-impact cross-tenant compromise paths.
Jul 24, 2026
TeamTNT abused an exposed Docker API to deploy a privileged Ubuntu container, mount the host filesystem, run cryptominers, and create a privileged SSH user. The group installed the legitimate **Weave Scope** Docker/Kubernetes administration tool, exposing its web dashboard on default port `4040` to map container environments and execute commands—effectively obtaining backdoor-like control through trusted software rather than custom malware. A compromised container can also become a path to cloud-account takeover through instance metadata services, pod IAM/AAD identities, embedded long-term cloud keys, and container escapes. Organizations should restrict Docker APIs and Weave Scope access, prevent pod access to metadata endpoints, enforce least-privilege workload identities and Kubernetes RBAC, eliminate long-term credentials from pods and secrets, remediate vulnerable workloads, and segment networks to limit lateral movement.
Sep 3, 2026