Improper access control in Azure Cosmos DB allows an unauthorized attacker to execute code over a network.
CVE-2026-66803
Score 10.0 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-30. a secondary CVSS source baseline 10.0; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 10.0
- EG Score
- 10.0(high)
- EG Risk
- 60(Track)EG Risk 60/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity100% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
July 30, 2026
Last Modified
July 31, 2026
Advisory Details (1)
Auto-updated Jul 31, 2026Security Update Guide - Microsoft Security Response Center
Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-66803Vendor Advisories for CVE-2026-66803(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(1)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 23× in last 7d / 23× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-31 23:00 UTCVendor advisory
- 2026-07-31 23:00 UTCGHSA enrichment
- 2026-07-31 19:17 UTCVendor advisory
- 2026-07-31 19:17 UTCGHSA enrichment
- 2026-07-31 15:33 UTCVendor advisory
- 2026-07-31 15:32 UTCGHSA enrichment
- 2026-07-31 11:47 UTCVendor advisory
- 2026-07-31 11:47 UTCGHSA enrichment
- 2026-07-31 08:03 UTCVendor advisory
- 2026-07-31 08:03 UTCGHSA enrichment
- 2026-07-31 04:19 UTCEG score recompute
- 2026-07-31 04:19 UTCVendor advisory
- 2026-07-31 04:19 UTCGHSA enrichment
- 2026-07-31 04:07 UTCEG score recompute
- 2026-07-31 04:07 UTCVendor advisory
- 2026-07-31 04:07 UTCGHSA enrichment
- 2026-07-31 02:03 UTCVendor advisory
- 2026-07-31 02:03 UTCGHSA enrichment
- 2026-07-30 22:20 UTCEG score recompute
- 2026-07-30 22:20 UTCGHSA enrichment
- 2026-07-30 21:27 UTCEG score recompute
- 2026-07-30 20:38 UTCEG score recompute
- 2026-07-30 20:36 UTCMITRE cvelistV5first tracked
Related CVEs(same vendor + same CWE)
Same vendor
10 shownmsrc
Same CWE
10 shownCWE-284
Frequently asked(4)
What is CVE-2026-66803?
When was CVE-2026-66803 disclosed?
What is the CVSS score of CVE-2026-66803?
How do I remediate CVE-2026-66803?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-66803
Is Your Infrastructure Affected by CVE-2026-66803?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.