CVE-2026-85922: Weak authentication in Azure Key Vault allows an unauthorized attacker to bypass a security feature over a net
48
This month
HIGH 7.4REMOTEWATCHLISTUPGRADEUPGRADEUPGRADE
CVE-2026-85922 is a high-severity flaw (CVSS 7.4) affecting azure-keyvault-administration, azure-keyvault-administration, azure-keyvault-certificates. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
Weak authentication in Azure Key Vault allows an unauthorized attacker to bypass a security feature over a network.
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
Verify at the official sourceNVD · CVE Program · Report a problem with this page Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2026-85922?
azure-keyvault-administration: upgrade to 1.0.1; azure-keyvault-administration: upgrade to 4.7.1; azure-keyvault-certificates: upgrade to 1.0.1. Exact commands for each OS are on this page.
Is CVE-2026-85922 being exploited?
CVE-2026-85922 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2026-85922 affect?
CVE-2026-85922 affects azure-keyvault-administration, azure-keyvault-administration, azure-keyvault-certificates. Severity is high (CVSS 7.4). Weak authentication in Azure Key Vault allows an unauthorized attacker to bypass a security feature over a network.
How urgent is CVE-2026-85922?
Priority 48/100. High severity; Remotely exploitable, no login, no user action; On your watchlist