Skip to content
Fencer Intel
high 7.4

CVE-2026-85922 json

Azure Key Vault Security Feature Bypass Vulnerability

published 29d ago modified yesterday also EUVD-2026-100126

cvss
7.4
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 49%
public exploits
0
none known

Summary

Weak authentication in Azure Key Vault allows an unauthorized attacker to bypass a security feature over a network.

Patch / fix

  • microsoft azure-keyvault-administration 1.0.1, 4.7.1
  • microsoft azure-keyvault-certificates 1.0.1, 4.11.2
  • microsoft azure-keyvault-keys 4.11.2
  • microsoft azure-keyvault-secrets 1.0.1, 4.11.2

Is CVE-2026-85922 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
last mo.

Exploit prediction

0.61% chance of exploitation in the next 30 days, higher than 49% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 7.4 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N/E:U/RL:O/RC:C
CNA 3.1 7.4 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected products

  • Microsoft azure_security_keyvault_certificates
  • Microsoft azure_security_keyvault_keys
  • Microsoft azure_security_keyvault_secrets
  • Microsoft azure-keyvault-administration
  • Microsoft azure-keyvault-certificates
  • Microsoft azure-keyvault-keys
  • Microsoft azure-keyvault-secrets
  • Microsoft azure-keyvault-securitydomain

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.