Unauthenticated security-feature bypass
Published Oct 13, 2026 · Updated Oct 13, 2026
Weak authentication in Microsoft Azure Key Vault allows remote attackers to bypass a security feature over a network. The supplied source record does not identify the failed authentication operation, and a matching public advisory was not retrieved. Package-specific applicability, additional attack preconditions, and consequences beyond security-feature bypass remain unverified.
Summary
What happened
Weak authentication in Microsoft Azure Key Vault allows remote attackers to bypass a security feature over a network. The supplied source record does not identify the failed authentication operation, and a matching public advisory was not retrieved. Package-specific applicability, additional attack preconditions, and consequences beyond security-feature bypass remain unverified.
The record
- CVE
- CVE-2026-85922
- Published
- Oct 13, 2026
- Updated
- Oct 13, 2026
- Vendor
- Microsoft Corporation
- Product
- Azure.Security.KeyVault.Secrets
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 13, 2026CVE publishedPublication date reported by the CVE source.
- Oct 13, 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 version<1.0.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started