Last updated: August 19, 2026 at 1:47 AM UTC
All 741 Vulnerability 286 Breach 129 Threat 319 Defense 7
Tag: cloud-security (2 articles)Clear

Azure Cosmos DB flaw exposed a master key that unlocked every customer database

Wiz Research disclosed CosmosEscape, a critical flaw chain in Microsoft's Azure Cosmos DB that could have given an attacker read and write access to every customer database on the service, including Microsoft's own. Starting from a crafted query against an attacker-controlled Gremlin database, the researchers escaped the query sandbox using .NET reflection, ran code on a shared gateway, and retrieved a platform-wide signing secret they call the Cosmos Master Key. That key let them fetch the access key for any Cosmos DB account on demand, reaching even private, network-isolated databases. Microsoft assigned CVE-2026-66803, fixed the issue across all regions, and found no evidence of abuse. Nothing needs patching by customers.

Check
No customer patching is required since Microsoft fixed this in the service, but review Cosmos DB access logs for unusual activity and consider rotating account keys as a precaution.
Affected
Azure Cosmos DB customers using the Gremlin API were at risk while the flaw was live; the exposed master key could reach any account's data across tenants, though Microsoft reports no abuse.
Fix
Treat this as a reminder that multi-tenant cloud isolation can fail: rotate Cosmos DB keys periodically, prefer short-lived credentials and network limits, and monitor database access.

Confused deputy weaknesses still expose cross-tenant access in major clouds

Researchers showed that confused deputy weaknesses persist in Google Cloud and Microsoft Azure, where a trusted service can be tricked into acting on an attacker's behalf against resources it should not reach. The pattern shows up when one service holds broad permissions and accepts instructions or identifiers from a less-trusted source without verifying who is really asking, which can enable cross-tenant access or privilege escalation. It is the same class of issue behind recent findings in enterprise agent and integration tooling, where a component with a user's permissions follows attacker-supplied input. The takeaway is architectural: identity and authorization must be checked at every trust boundary, not assumed from the calling service.

Check
Review cloud integrations and automation where one service acts for another, and confirm each checks the real caller's identity and authorization rather than trusting the upstream service.
Affected
Organizations relying on cloud services and integrations that pass identifiers or instructions between trust boundaries; a broadly permissioned service can be steered into cross-tenant access or privilege escalation.
Fix
Scope service permissions tightly, validate the originating identity at every boundary, use per-tenant isolation and unique unguessable identifiers, and monitor for a trusted service accessing resources outside its expected scope.