Evidence used
- No CISA KEV confirmation is currently recorded.
- EPSS is 0.63% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2026
CVE-2026-69857High confidence
Azure Cosmos DB Spoofing Vulnerability
Microsoft · Azure Cosmos DB
8.5HighCVSS 3.1
Within 7 days
Patch availableHigh technical severity; prioritise exposed affected systems while verifying vendor guidance.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityHigh→Operational priority:High, unchanged from published severity.unchanged
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict the affected network interface to trusted sources where business-safe.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs Microsoft Azure Cosmos DB and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
High technical severity; prioritise exposed affected systems while verifying vendor guidance.
Patch available01
What, why and how
Authorization bypass through user-controlled key in Azure Cosmos DB allows an authorized attacker to perform spoofing over a network.
What
Authorization bypass through user-controlled key in Azure Cosmos DB allows an authorized attacker to perform spoofing over a network.
Why
The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
How
An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
Authorization bypass through user-controlled key in Azure Cosmos DB allows an authorized attacker to perform spoofing over a network.
Why
The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
How
An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- a network path → Authorization Bypass Through User-Controlled Key → cause the confidentiality, integrity or availability impact described by the vendor
- Attack surface
- Network
- Privileges required
- Low: a basic authenticated account is required
- User interaction
- None
- Attack complexity
- High: exploitation depends on specific conditions
- Security boundary
- Changed: exploitation can affect a different security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-639 ↗
CWE-639: Authorization Bypass Through User-Controlled Key. The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H/E:U/RL:O/RC:CCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SChangedScope: The attack can affect a component governed by a different security authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.- Post-exploitation / living off the land
- No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Patch available
- Affected
- Azure Cosmos DB: -
- Action
- Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
- Workaround
- No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04
Evidence and provenance
Published 3 Sept 2026 · Last source change 1 Oct 2026, 22:52 UTC · CWE-639 · Authorization Bypass Through User-Controlled Key
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-09-04
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2026-70796
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceOther authority
NVD statusNVD enriched
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- Vendor guidanceAuthoritative vendor guidance changed: removed remediation: acn.gov.it/aggiornamenti-mensili-microsoft-24.secure@microsoft.com ↗
- Before
- remediation: acn.gov.it/aggiornamenti-mensili-microsoft-24 · vendor advisory: msrc.microsoft.com/CVE-2026-69857
- After
- vendor advisory: msrc.microsoft.com/CVE-2026-69857
- Remediation statusRemediation status changed from Mitigation available to Awaiting fix.secure@microsoft.com ↗
- Before
- Mitigation available
- After
- Awaiting fix
- Vendor guidanceAuthoritative vendor guidance changed: removed remediation: acn.gov.it/aggiornamenti-mensili-microsoft-24.secure@microsoft.com ↗
- Before
- remediation: acn.gov.it/aggiornamenti-mensili-microsoft-24 · vendor advisory: msrc.microsoft.com/CVE-2026-69857
- After
- vendor advisory: msrc.microsoft.com/CVE-2026-69857
- Remediation statusRemediation status changed from Mitigation available to Awaiting fix.secure@microsoft.com ↗
- Before
- Mitigation available
- After
- Awaiting fix
- Vendor guidanceAuthoritative vendor guidance changed: removed remediation: acn.gov.it/aggiornamenti-mensili-microsoft-24.secure@microsoft.com ↗
- Before
- remediation: acn.gov.it/aggiornamenti-mensili-microsoft-24 · vendor advisory: msrc.microsoft.com/CVE-2026-69857
- After
- vendor advisory: msrc.microsoft.com/CVE-2026-69857
- Remediation statusRemediation status changed from Mitigation available to Awaiting fix.secure@microsoft.com ↗
- Before
- Mitigation available
- After
- Awaiting fix
- Vendor guidanceAuthoritative vendor guidance changed: removed remediation: acn.gov.it/aggiornamenti-mensili-microsoft-24.secure@microsoft.com ↗
- Before
- remediation: acn.gov.it/aggiornamenti-mensili-microsoft-24 · vendor advisory: msrc.microsoft.com/CVE-2026-69857
- After
- vendor advisory: msrc.microsoft.com/CVE-2026-69857
- Remediation statusRemediation status changed from Mitigation available to Awaiting fix.secure@microsoft.com ↗
- Before
- Mitigation available
- After
- Awaiting fix
- Vendor guidanceAuthoritative vendor guidance changed: removed remediation: acn.gov.it/aggiornamenti-mensili-microsoft-24.secure@microsoft.com ↗
- Before
- remediation: acn.gov.it/aggiornamenti-mensili-microsoft-24 · vendor advisory: msrc.microsoft.com/CVE-2026-69857
- After
- vendor advisory: msrc.microsoft.com/CVE-2026-69857
- Remediation statusRemediation status changed from Mitigation available to Awaiting fix.secure@microsoft.com ↗
- Before
- Mitigation available
- After
- Awaiting fix
- Vendor guidanceAuthoritative vendor guidance changed: removed remediation: acn.gov.it/aggiornamenti-mensili-microsoft-24.secure@microsoft.com ↗
- Before
- remediation: acn.gov.it/aggiornamenti-mensili-microsoft-24 · vendor advisory: msrc.microsoft.com/CVE-2026-69857
- After
- vendor advisory: msrc.microsoft.com/CVE-2026-69857
- Remediation statusRemediation status changed from Mitigation available to Awaiting fix.secure@microsoft.com ↗
- Before
- Mitigation available
- After
- Awaiting fix
- Vendor guidanceAuthoritative vendor guidance changed: removed remediation: acn.gov.it/aggiornamenti-mensili-microsoft-24.secure@microsoft.com ↗
- Before
- remediation: acn.gov.it/aggiornamenti-mensili-microsoft-24 · vendor advisory: msrc.microsoft.com/CVE-2026-69857
- After
- vendor advisory: msrc.microsoft.com/CVE-2026-69857
- Remediation statusRemediation status changed from Mitigation available to Awaiting fix.secure@microsoft.com ↗
- Before
- Mitigation available
- After
- Awaiting fix
- Vendor guidanceAuthoritative vendor guidance changed: removed remediation: acn.gov.it/aggiornamenti-mensili-microsoft-24.secure@microsoft.com ↗
- Before
- remediation: acn.gov.it/aggiornamenti-mensili-microsoft-24 · vendor advisory: msrc.microsoft.com/CVE-2026-69857
- After
- vendor advisory: msrc.microsoft.com/CVE-2026-69857
- Remediation statusRemediation status changed from Mitigation available to Awaiting fix.secure@microsoft.com ↗
- Before
- Mitigation available
- After
- Awaiting fix
- Vendor guidanceAuthoritative vendor guidance changed: removed remediation: acn.gov.it/aggiornamenti-mensili-microsoft-24.secure@microsoft.com ↗
- Before
- remediation: acn.gov.it/aggiornamenti-mensili-microsoft-24 · vendor advisory: msrc.microsoft.com/CVE-2026-69857
- After
- vendor advisory: msrc.microsoft.com/CVE-2026-69857
- Remediation statusRemediation status changed from Mitigation available to Awaiting fix.secure@microsoft.com ↗
- Before
- Mitigation available
- After
- Awaiting fix
- Vendor guidanceAuthoritative vendor guidance changed: removed remediation: acn.gov.it/aggiornamenti-mensili-microsoft-24.secure@microsoft.com ↗
- Before
- remediation: acn.gov.it/aggiornamenti-mensili-microsoft-24 · vendor advisory: msrc.microsoft.com/CVE-2026-69857
- After
- vendor advisory: msrc.microsoft.com/CVE-2026-69857
- Remediation statusRemediation status changed from Mitigation available to Awaiting fix.secure@microsoft.com ↗
- Before
- Mitigation available
- After
- Awaiting fix
- Vendor guidanceAuthoritative vendor guidance changed: removed remediation: acn.gov.it/aggiornamenti-mensili-microsoft-24.secure@microsoft.com ↗
- Before
- remediation: acn.gov.it/aggiornamenti-mensili-microsoft-24 · vendor advisory: msrc.microsoft.com/CVE-2026-69857
- After
- vendor advisory: msrc.microsoft.com/CVE-2026-69857
- Remediation statusRemediation status changed from Mitigation available to Awaiting fix.secure@microsoft.com ↗
- Before
- Mitigation available
- After
- Awaiting fix
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- Before
- - · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- After
- Azure Cosmos DB: - · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- Remediation statusRemediation status changed from Awaiting fix to Mitigation available.CSIRT Italia ↗
- Before
- Awaiting fix
- After
- Mitigation available
- Vendor guidanceAuthoritative vendor guidance changed: added vendor advisory: msrc.microsoft.com/CVE-2026-69857.secure@microsoft.com ↗
- Before
- no authoritative guidance recorded
- After
- vendor advisory: msrc.microsoft.com/CVE-2026-69857
- ENISA EUVD mappingEUVD-2026-70796 was added to the official ENISA EUVD mapping for this CVE.ENISA EUVD ↗
- Before
- not recorded
- After
- {"euvdId":"EUVD-2026-70796"}
- Catalogue recordCVE added to the BlackTree catalogue.CNA ↗
CVE published
Remediation guidance recorded
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.