Secuno
ENNL
Book demo

CVE-2026-66803

Microsoft Azure Cosmos Db broken access control

10.0 CRITICALEPSS 0.90%
  1. Published30 Jul 2026

Description

Improper access control in Azure Cosmos DB allows an unauthorized attacker to execute code over a network.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionNone
ScopeChanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Affected products

Microsoft Azure Cosmos Dball versions

Remediation

No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-1075109.1
An authenticated high privilege user can inject arguments in troubleshooting commands…
CVE-2026-764989.8
As part of Cisco's ongoing commitment to proactive security and product quality, the…
CVE-2026-764638.8
As part of Cisco's ongoing commitment to proactive security and product quality, the…
CVE-2026-764559.8
As part of Cisco's ongoing commitment to proactive security and product quality, the…
CVE-2026-976808.3
IBM Langflow OSS 1.0.0 through 1.12.2 could allow a remote authenticated attacker to…
CVE-2026-1043358.8
IBM Langflow OSS 1.0.0 through 1.12.2 could allow a remote authenticated attacker to…

Frequently asked

Is CVE-2026-66803 being actively exploited?

CVE-2026-66803 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.90%.

How severe is CVE-2026-66803?

CVE-2026-66803 has a CVSS 3.1 base score of 10.0, rated critical. EPSS estimates a 0.90% probability of exploitation.

Which products are affected by CVE-2026-66803?

Affected products include Microsoft Azure Cosmos Db.

How do I fix CVE-2026-66803?

Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-66803 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.