Azure Key Vault Security Feature Bypass Vulnerability
CVE-2026-85922 · published 13 Oct 2026
How serious is it
- Severity: high, CVSS score 7.4 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2026-85922?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- Microsoft azure_security_keyvault_certificates: 1.0.1 to < 1.0.1
- Microsoft azure_security_keyvault_keys: 1.0.1 to < 1.0.1
- Microsoft azure_security_keyvault_secrets: 1.0.1 to < 1.0.1
- Microsoft azure-keyvault-administration: 4.7.1 to < 4.7.1
- Microsoft azure-keyvault-certificates: 4.11.2 to < 4.11.2
- Microsoft azure-keyvault-keys: 4.11.2 to < 4.11.2
- Microsoft azure-keyvault-secrets: 4.11.2 to < 4.11.2
- Microsoft azure-keyvault-securitydomain: 1.0.0b3 to < 1.0.0b3
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
Weak authentication in Azure Key Vault allows an unauthorized attacker to bypass a security feature over a network.
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
Merged from CVE List. Last updated 23 Oct 2026. All vulnerabilities · RSS · JSON