CVE-2026-85922
Azure Key Vault Security Feature Bypass Vulnerability
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.0.1, 4.7.1, 4.11.2, 1.0.0b3
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
Weak authentication in Azure Key Vault allows an unauthorized attacker to bypass a security feature over a network.
Timeline
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- CVE published
- Record last updated
Affected versions
- Microsoft azure_security_keyvault_certificates
From 1.0.1 · fixed in 1.0.1
- Microsoft azure_security_keyvault_keys
From 1.0.1 · fixed in 1.0.1
- Microsoft azure_security_keyvault_secrets
From 1.0.1 · fixed in 1.0.1
- Microsoft azure-keyvault-administration
From 4.7.1 · fixed in 4.7.1
- Microsoft azure-keyvault-certificates
From 4.11.2 · fixed in 4.11.2
- Microsoft azure-keyvault-keys
From 4.11.2 · fixed in 4.11.2
- Microsoft azure-keyvault-secrets
From 4.11.2 · fixed in 4.11.2
- Microsoft azure-keyvault-securitydomain
From 1.0.0b3 · fixed in 1.0.0b3