Critical Azure Cosmos DB flaw risked cross-tenant compromise

A now-patched critical flaw in Azure Cosmos DB could have been exploited to compromise every database in the service, including Microsoft’s own internal databases for Entra ID, Teams, and Copilot, potentially creating a widespread cross-service attack.

In a July 30 blog post, Wiz Research reported on CosmosEscape, a flaw in which attackers could have acquired the Cosmos Master Key, a platformwide secret that grants two powerful capabilities:

Security pros said the reason this story has gotten so much attention was its potential scale: A flaw in shared cloud infrastructure could theoretically affect hundreds, if not thousands, of organizations at once, and that’s why researchers disclosed it so prominently.

“While Microsoft says the vulnerability has been fully patched and there’s no evidence of customer impact, it's an important reminder that no cloud provider is immune to security flaws,” said Chris Lentricchia, director of cloud and AI security strategy at Sweet Security. “The key challenge for security teams is quickly determining what, if anything, in their own environment was actually exposed. Understanding real business impact, rather than treating every critical advisory the same, is what lets organizations respond with confidence."

John Gallagher, vice president at Viakoo, explained that a vulnerability that allows cross-tenant access or remote code execution within a central platform service breaks the core security architecture of cloud infrastructure — that it’s in Microsoft Azure further compounds the attention.

Gallagher added that traditional security tools would not find this, and the blast radius was potentially enormous in that it could have impacted not just IT, but OT and IoT systems.

“While Microsoft fixed the underlying vulnerability on the platform side — meaning customers do not need to install a patch — security teams should not treat this as a ‘zero-action’ event,” said Gallagher. “Organizations should review their security posture, assess their defense-in-depth measures, and ensure they have the ability to rapidly remediate all types of systems whether IT, OT, or IoT.

Trey Ford, chief strategy and trust officer at Bugcrowd, said nothing here requires customer action today, and that's precisely the takeaway leadership should note. However, Ford said when the fix, the forensics, and the assurance all come from one vendor, we're not managing risk — we're trusting it.

Ford said the right question for CISOs isn't "Are we patched?"; it’s "How much of our risk model rests on someone else's homework?"

“This is what happens when a single research team, working faster than any internal audit cycle, finds the seam before a criminal does,” said Ford. “Wiz caught a flaw that could cascade upward into services like Teams and Copilot. This is the asymmetry of the moment: attackers move at machine speed, and the only defense that matches it is a blend of agentic and humans hunting continuously, not annually.”

Robert Costello, chief digital and information officer at the Merlin Group, said this discovery underscores the value of cloud security research, particularly as the rise of AI has accelerated the pace and sophistication of vulnerability discovery, making attack surface management more critical than ever.

Costello said Wiz identified and responsibly disclosed a high-impact vulnerability, allowing time to remediate before attackers could broadly exploit it.

“The complexity of this flaw, and its potential to expose every Cosmos DB instance is a reminder that even the largest cloud providers must constantly test their own environments,” said Costello. “This demonstrates why continuous cloud posture visibility and close vendor collaboration are essential to protecting modern cloud environments.”