Azure Cosmos DB flaw let attackers reach any tenant database, including Microsoft own
Azure Cosmos DB flaw let attackers reach any tenant’s database, including Microsoft’s own
Wiz researchers found a vulnerability chain in Azure Cosmos DB that could have let attackers break out of the Gremlin query sandbox, grab a platform wide master key, and access any customer’s database. The affected databases included those backing Entra ID, Teams, and Copilot.
The vulnerability chain
The exploit, dubbed CosmosEscape, started in the Gremlin API, one of several query interfaces Cosmos DB supports. Yuval Avrahami and Lior Maman at Wiz noticed .NET exceptions leaking during testing. Those exceptions suggested Microsoft’s custom Gremlin engine had insufficient restrictions around .NET reflection.
Abusing reflection let the researchers escape the Gremlin sandbox and run arbitrary code on the Cosmos DB Database Gateway, the service that executes customer queries. From there they accessed credentials that could retrieve the primary key for any Cosmos DB account, not just their own.
A master key that worked everywhere
The compromised credential — what Wiz calls the “Cosmos Master Key” — worked across tenants, regions, and API flavors including SQL, MongoDB, Cassandra, and Gremlin. It also unlocked Cosmos DB’s regional configuration store, letting attackers enumerate database accounts by tenant or subscription ID before pulling their primary keys.
Because Cosmos DB underpins several Microsoft cloud services, databases supporting Entra ID, Teams, and Copilot were potentially accessible. Even private and network isolated Cosmos DB deployments were exposed, since the compromised Database Gateway was responsible for enforcing those network boundaries.
Microsoft’s response
Wiz disclosed privately on November 20, 2025. Microsoft blocked the vulnerable Gremlin attack path within 48 hours and completed a broader architectural redesign across all Azure regions by July 2026. The company says its investigation found no evidence of unauthorized activity beyond the researchers’ testing, no customer data was accessed, and no customer action is required. Microsoft also eliminated the platform wide authentication mechanism Wiz dubbed the “Cosmos Master Key.”
What this means for African enterprises
Microsoft says customers don’t need to take immediate action. But the disclosure highlights risks that exist below the security controls cloud customers typically manage. As IDC’s Sakshi Grover puts it, CosmosEscape shows that tenant isolation can fail below the layers customers can configure or monitor.
Instead of evaluating managed database services primarily on encryption, private networking, or identity controls, enterprises should examine how providers isolate tenant controlled execution from privileged service components, how they scope internal credentials, and how they limit the damage when shared infrastructure is compromised.
Organizations using the Cosmos DB Gremlin API should review available logs, determine whether sensitive workloads were affected, and seek additional assurance from Microsoft where regulatory or compliance requirements demand it. The incident should also push organizations to reduce reliance on static database account keys. Managed identities, fine grained role based access controls, and client side encryption are practical alternatives.
The bigger picture
Large cloud services depend on privileged gateways, control planes, metadata stores, and service identities that operate across large numbers of customers. When tenant controlled input gets processed close to those components, a vulnerability can cross what appeared to be separate security boundaries and create consequences at platform scale.
This isn’t just a Microsoft problem. Every major cloud provider runs similar privileged infrastructure. The CosmosEscape research proves the trust boundary between customer workloads and provider control planes is thinner than most security teams assume.
Cloud vendors harden their control planes. That’s their job. But eHawu’s WireGuard mesh gives African enterprises cryptographic network isolation that doesn’t depend on a provider’s internal architecture. Your traffic never traverses shared gateway infrastructure. Your credentials never touch a platform wide master key. When the control plane fails, your network segmentation still holds.
