Authenticated spoofing via user-controlled authorization key
Published Sep 3, 2026 · Updated Sep 4, 2026
Authorization bypass in Microsoft Azure Cosmos DB allows remote authenticated users to spoof identities through a user-controlled key. Microsoft has not disclosed which Cosmos DB API or authorization check accepts the user-controlled key without verifying the caller's entitlement. A valid low-privilege credential and high-complexity conditions are required; the disclosed consequence is network-reachable spoofing, while the affected data or identity boundary remains undisclosed.
Summary
What happened
Authorization bypass in Microsoft Azure Cosmos DB allows remote authenticated users to spoof identities through a user-controlled key. Microsoft has not disclosed which Cosmos DB API or authorization check accepts the user-controlled key without verifying the caller's entitlement. A valid low-privilege credential and high-complexity conditions are required; the disclosed consequence is network-reachable spoofing, while the affected data or identity boundary remains undisclosed.
The record
- CVE
- CVE-2026-69857
- Published
- Sep 3, 2026
- Updated
- Sep 4, 2026
- Vendor
- Microsoft
- Product
- Azure Cosmos DB
- Classifications
- CWE-639, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 3, 2026CVE publishedPublication date reported by the CVE source.
- Sep 4, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=-
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo