Azure Cosmos DB Flaw Exposed Platform-Wide Key That Could Access Any Database

A now-patched vulnerability in Azure Cosmos DB could have let an attacker escape the service's Gremlin query sandbox and obtain full read and write access to databases across customer tenants, according to Wiz. Wiz, which codenamed the chain CosmosEscape, said the exploit chain began with a crafted query against a Gremlin database controlled by the attacker. From there, code execution on a

According to Wiz, the CosmosEscape vulnerability chain in Azure Cosmos DB allowed a crafted Gremlin query to escape the query sandbox, achieve code execution on a multi-tenant gateway, and expose a platform-wide signing secret plus regional account directories, enabling retrieval of any tenant’s primary account key before Microsoft patched and later eliminated the master key.[1][5] Microsoft reports no evidence of malicious exploitation beyond researcher testing and states no customer action is required for this specific flaw.[1] From a RealGround perspective, this highlights a severe multi-tenant SaaS risk where a single control-plane or platform-wide secret can enable cross-tenant data compromise, including AI-related databases used by services like Copilot and Entra ID.[5] Organizations using Cosmos DB for AI workloads or agent data stores should apply continuous red teaming against cloud control-plane paths, enforce strong key-rotation and least-privilege designs, and demand SBOM-level visibility into cloud features (e.g., Gremlin, notebooks) that can introduce cross-tenant breakout risks.