Loading story…
Wiz disclosed ChaosDB, a critical cross-tenant vulnerability chain in Azure Cosmos DB's Jupyter Notebook feature. Misconfigurations let notebook C# code execute as root, bypass container-local firewall controls, and reach Azure instance metadata and WireServer services on shared hosts. Researchers obtained certificates and private keys, authenticated to Azure Service Fabric, and decrypted Cosmos DB primary keys, notebook tokens, and storage-account credentials belonging to other customers. The exposed Cosmos DB keys enabled persistent full read, write, and delete access to affected accounts, and Wiz reported access to databases associated with several thousand Azure customers.
Microsoft disabled the vulnerable notebook service within 48 hours of the August 2021 report and later confirmed that several thousand customers were affected; it revoked some credentials and notified more than 30% of Cosmos DB customers to rotate keys. Organizations with Jupyter Notebooks enabled—especially accounts permitting external or cross-tenant network access—were advised to regenerate primary keys, restrict network exposure, move from shared keys to RBAC, and use private endpoints. Wiz later used ChaosDB to introduce PEACH, a tenant-isolation assessment framework covering Privilege, Encryption, Authentication, Connectivity, and Hygiene to identify and harden cross-tenant boundaries in cloud applications.
See affected versions and whether adversaries are exploiting it.
9 events from the most recent confirmed update back to the earliest known activity.
Microsoft confirmed that several thousand customers were affected by the ChaosDB issue.
Microsoft Security Response Center confirmed the reported behavior, and Wiz observed that some credentials obtained during its research were revoked the same day.
Microsoft disabled the vulnerable Cosmos DB Jupyter Notebook service after Wiz's report, pending a security redesign.
Wiz notified Microsoft about ChaosDB, a cross-tenant vulnerability chain that could expose Cosmos DB primary keys and grant full read, write, and delete access to affected customer accounts.
Wiz first exploited flaws in Cosmos DB's Jupyter Notebook environment, escalating to root, bypassing container firewall rules, and obtaining access to shared-host Azure services and credentials. The researchers ultimately accessed other customers' Cosmos DB keys and infrastructure data.
Microsoft began automatically enabling the Jupyter Notebook feature for newly created Cosmos DB accounts. The feature would be automatically disabled if unused during its initial three-day period.
Microsoft introduced the Jupyter Notebook feature for Azure Cosmos DB, enabling customers to visualize data and create customized views.
Wiz introduced PEACH, a framework for assessing tenant isolation in multi-tenant cloud applications across privilege, encryption, authentication, connectivity, and hygiene controls. Wiz retrospectively applied it to ChaosDB and identified isolation-design and implementation gaps that enabled the attack path.
Microsoft notified more than 30% of Cosmos DB customers that they needed to manually rotate access keys, while Wiz urged potentially exposed customers to regenerate keys because primary keys could have been retained by attackers.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
6 references tracked. Mallory keeps watching after this page renders.
peach.wiz.io
Open sourcewiz.io
Open sourceyoutube.com
Open sourcewiz.io
Open sourcewiz.io
Open sourcewiz.io
Open sourceMap 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 patched a critical Azure Cosmos DB vulnerability that researchers said could have enabled **cross-tenant database takeover** by exposing a platform-wide signing secret. Wiz, which dubbed the exploit chain `CosmosEscape`, reported that an attacker with only a standard Azure account and an attacker-controlled Cosmos DB Gremlin database could escape the Gremlin query sandbox, achieve code execution on a multi-tenant gateway, and obtain a key capable of accessing other customers’ databases. According to the disclosure, the exposed secret could be used to retrieve primary account keys across tenants, regions, and multiple Cosmos DB API variants, including **SQL, MongoDB, Cassandra, and Gremlin**, potentially affecting even private or network-isolated accounts. Microsoft said it blocked the vulnerable Gremlin input within 48 hours of disclosure in November 2025, completed a permanent global fix in July 2026, and removed the platform-wide key; the company added that it found no evidence of customer impact or unauthorized activity beyond the researchers’ testing and said no customer action was required.
Aug 6, 2026
Microsoft has patched a critical Azure Cosmos DB vulnerability chain dubbed **CosmosEscape** that could have let an attacker move from a crafted **Gremlin API** query to code execution on a multi-tenant backend component and ultimately obtain secrets capable of accessing virtually any customer Cosmos DB account. Wiz reported that insufficient restrictions around .NET reflection allowed escape from the Gremlin sandbox, exposing a platform-wide signing secret—described as the **Cosmos Master Key**—and a regional account directory that could be used to locate target accounts and retrieve their primary keys. With those primary keys, an attacker could have gained full read and write control over Cosmos DB deployments across **SQL, MongoDB, Cassandra, and Gremlin** APIs, including private databases across regions and potentially data tied to Microsoft services such as **Entra ID, Teams, and Copilot**. Microsoft said it blocked the vulnerable Gremlin entry point within 48 hours of Wiz’s November 2025 report, later completed broader fixes across all regions, removed the shared platform-wide key, and added controls to prevent similar backend access; the company said its review found no evidence of exploitation or customer data access beyond the researchers’ testing, and no customer action is required.
Jul 31, 2026
JFrog Security Research disclosed four vulnerabilities in the Chaos Mesh chaos-engineering platform that can let attackers with in-cluster network access compromise Kubernetes environments, including three critical command-injection bugs and one authentication bypass. The issues, tracked as **CVE-2025-59358**, **CVE-2025-59359**, **CVE-2025-59360**, and **CVE-2025-59361**, affect Chaos Mesh deployments prior to **2.7.3** and stem from an exposed unauthenticated GraphQL server plus unsafe shell command construction in the `cleanTcs`, `killProcesses`, and `cleanIptables` mutations. JFrog said the default configuration can expose the GraphQL interface to any pod on the cluster, allowing even an unprivileged workload to reach vulnerable operations. Researchers reported that the flaws can be chained to invoke fault injections, execute arbitrary commands on pods and nodes, steal Kubernetes service account tokens, move laterally, and potentially take over an entire cluster. The command-injection bugs were rated **CVSS 9.8** and are especially dangerous because Chaos Mesh components such as the Controller Manager and Chaos Daemon typically run with elevated privileges. Chaos Mesh has issued fixes, including changes referenced in GitHub pull request **#4702**, and JFrog urged users to upgrade immediately to **Chaos Mesh 2.7.3** or disable the controller server through Helm as a temporary mitigation; platforms that integrate Chaos Mesh, including **Azure Chaos Studio for AKS**, may also be exposed.
Jun 29, 2026