Quick answers
- Is CVE-2026-85925 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-85925 being exploited in the wild.
- How severe is CVE-2026-85925?
- High severity, with a CVSS score of 8.2, published 13 October 2026.
- Which products and versions are affected?
- Microsoft Azure Key Vault.
- Is there a fix for CVE-2026-85925?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-85925 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-85925?
- Check whether you run Microsoft Azure Key Vault, Microsoft Azure-Keyvault-Administration, Microsoft Azure-Keyvault-Certificates or one of the others listed. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability involves improper restriction of communication channels to intended endpoints in Azure Key Vault, allowing an authenticated network attacker to perform privilege escalation. The attack requires an existing authorized account but does not require user interaction. A successful exploit grants the attacker elevated privileges within the Key Vault environment, potentially allowing access to secrets and keys beyond their intended scope.
Affected products
- Microsoft Azure Key Vault
Timeline
- 2026-10-13: disclosed