Quick answers
- Is CVE-2026-66803 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-66803 being exploited in the wild.
- How severe is CVE-2026-66803?
- Critical severity, with a CVSS score of 10, published 30 July 2026.
- Which products and versions are affected?
- Microsoft Azure Cosmos DB All versions.
- Is there a fix for CVE-2026-66803?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-66803 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-66803?
- Check whether you run Microsoft Azure Cosmos DB at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A vulnerability classified as improper access control (CWE-284) exists in Microsoft Azure Cosmos DB. The flaw allows an unauthenticated attacker to achieve remote code execution (RCE) via a network-based attack vector. According to the CVSS 3.1 score of 10.0, the attack has low complexity, requires no user interaction, and results in a 'Changed' scope, indicating the attacker can impact components beyond the database itself. Microsoft has acknowledged the issue, and users are advised to consult the Microsoft Security Response Center (MSRC) for mitigation and patching guidance.
Affected products
- Microsoft Azure Cosmos DB All versions
Timeline
- 2026-07-30: disclosed: Initial disclosure by Microsoft and NVD publication.