Quick answers
- Is CVE-2026-62825 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-62825 being exploited in the wild.
- How severe is CVE-2026-62825?
- Critical severity, with a CVSS score of 10, published 24 July 2026.
- Which products and versions are affected?
- Microsoft Azure Key Vault All versions.
- Is there a fix for CVE-2026-62825?
- 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-62825 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-62825?
- Check whether you run Microsoft Azure Key Vault at an affected version. 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
A vulnerability classified as improper authentication (CWE-287) exists within Microsoft Azure Key Vault. The flaw allows a remote, unauthenticated attacker to bypass security controls and elevate their privileges within the service environment. According to the CVSS vector, the attack can be carried out over the network with low complexity and requires no user interaction. Successful exploitation grants the attacker high-impact capabilities to modify or destroy resources (Integrity and Availability), though the specific vector indicates no direct impact on Confidentiality. As this is an exclusively hosted service, Microsoft typically manages the deployment of fixes directly to the Azure infrastructure.
Affected products
- Microsoft Azure Key Vault All versions
Timeline
- 2026-07-24: advisory: Initial disclosure by Microsoft and NVD