Executive Summary
In November 2025, security researchers at Wiz identified a critical vulnerability in Microsoft Azure's Cosmos DB, dubbed 'CosmosEscape'. This flaw allowed attackers to escape the Gremlin query sandbox, execute arbitrary code on multi-tenant gateways, and access a platform-wide signing secret. Exploiting this, attackers could retrieve primary account keys, granting full read and write access to databases across customer tenants. Microsoft promptly blocked the vulnerable Gremlin entry point within 48 hours of the report and completed a comprehensive fix by July 2026, eliminating the platform-wide key. Investigations revealed no unauthorized access to customer data during this period.
This incident underscores the critical importance of robust isolation mechanisms in multi-tenant cloud services. As cloud adoption continues to rise, ensuring the security of shared resources becomes paramount to prevent potential cross-tenant vulnerabilities.
Why This Matters Now
The 'CosmosEscape' vulnerability highlights the ongoing challenges in securing multi-tenant cloud environments. As organizations increasingly rely on cloud services, understanding and mitigating such risks is essential to protect sensitive data and maintain trust in cloud platforms.
Attack Path Analysis
An attacker exploited a vulnerability in Azure Cosmos DB's Gremlin query sandbox to achieve code execution on a multi-tenant gateway, leading to unauthorized access to customer databases across tenants.
Kill Chain Progression
Initial Compromise
Description
The attacker crafted a malicious Gremlin query targeting their own Azure Cosmos DB instance, exploiting a flaw in the query sandbox to execute arbitrary code.
Related CVEs
CVE-2025-64675
CVSS 9.6A cross-site scripting (XSS) vulnerability in Azure Cosmos DB allows unauthorized attackers to perform spoofing attacks over a network.
Affected Products:
Microsoft Azure Cosmos DB – -
Exploit Status:
no public exploit
MITRE ATT&CK® Techniques
Exploit Public-Facing Application
Abuse Elevation Control Mechanism: Temporary Elevated Cloud Access
Valid Accounts: Cloud Accounts
Account Access Removal
Data from Cloud Storage Object
Potential Compliance Exposure
Mapping incident impact across multiple compliance frameworks.
PCI DSS 4.0 – Security of System Components
Control ID: 6.4.1
NYDFS 23 NYCRR 500 – Cybersecurity Policy
Control ID: 500.03
DORA – ICT Risk Management Framework
Control ID: Article 5
CISA ZTMM 2.0 – Identity and Access Management
Control ID: 3.1
NIS2 Directive – Security Measures
Control ID: Article 21
Sector Implications
Industry-specific impact of the vulnerabilities, including operational, regulatory, and cloud security risks.
Financial Services
Azure Cosmos DB cloud misconfiguration enabling cross-tenant database access threatens sensitive financial data, requiring enhanced zero trust segmentation and egress security controls.
Health Care / Life Sciences
Platform-wide database access vulnerability exposes protected health information across tenants, demanding stricter HIPAA compliance through multicloud visibility and encrypted traffic capabilities.
Computer Software/Engineering
CosmosEscape exploit targeting Gremlin query sandbox affects cloud-native applications, necessitating Kubernetes security frameworks and cloud native security fabric implementation for protection.
Government Administration
Cross-tenant database exposure in Azure cloud services threatens government data integrity, requiring immediate threat detection systems and secure hybrid connectivity for sensitive operations.
Sources
- Azure Cosmos DB Flaw Exposed Platform-Wide Key That Could Access Any Databasehttps://thehackernews.com/2026/07/azure-cosmos-db-flaw-exposed-platform.htmlVerified
- CVE-2025-64675: Azure Cosmos DB Spoofing Vulnerabilityhttps://askarlabs.com/cve/CVE-2025-64675/Verified
- Microsoft warns customers that Azure Cosmos DB vulnerability exposed their databases for yearshttps://www.techspot.com/news/90981-microsoft-warns-customers-azure-cosmos-db-vulnerability-exposed.htmlVerified
Frequently Asked Questions
Cloud Native Security Fabric Mitigations and ControlsCNSF
Aviatrix Zero Trust CNSF is pertinent to this incident as it could have limited the attacker's ability to exploit vulnerabilities and move laterally across tenant databases, thereby reducing the potential blast radius.
Control: Cloud Native Security Fabric (CNSF)
Mitigation: The attacker's ability to execute arbitrary code on the multi-tenant gateway would likely have been constrained, reducing the risk of initial compromise.
Control: Zero Trust Segmentation
Mitigation: The attacker's ability to escalate privileges and access other tenants' databases would likely have been constrained, reducing the scope of unauthorized access.
Control: East-West Traffic Security
Mitigation: The attacker's ability to move laterally within the Azure Cosmos DB infrastructure would likely have been constrained, reducing the risk of accessing additional customer databases.
Control: Multicloud Visibility & Control
Mitigation: The attacker's ability to establish command and control over compromised databases would likely have been constrained, reducing the risk of data manipulation across customer accounts.
Control: Egress Security & Policy Enforcement
Mitigation: The attacker's ability to exfiltrate sensitive customer data to external systems would likely have been constrained, reducing the risk of data breaches.
The overall impact of unauthorized access, including data breaches and service disruptions, would likely have been constrained, reducing the potential damage to affected customers.
Impact at a Glance
Affected Business Functions
- Database Management
- Data Security
- Application Development
Estimated downtime: N/A
Estimated loss: N/A
Potential exposure of sensitive customer data due to unauthorized access.
Recommended Actions
Key Takeaways & Next Steps
- • Implement Zero Trust Segmentation to enforce strict access controls and limit lateral movement within the network.
- • Enhance Threat Detection & Anomaly Response capabilities to identify and respond to unusual activities promptly.
- • Utilize Inline IPS (Suricata) to detect and prevent exploitation attempts targeting known vulnerabilities.
- • Apply Multicloud Visibility & Control to monitor and manage security policies across different cloud environments.
- • Regularly review and update security configurations to address potential vulnerabilities and ensure compliance with security standards.



