CVE-2026-85925: Improper restriction of communication channel to intended endpoints in Azure Key Vault allows an authorized at

Q: How do I fix CVE-2026-85925?

azure-keyvault-administration: upgrade to 4.8.1; azure-keyvault-certificates: upgrade to 4.9.1; azure-keyvault-keys: upgrade to 4.10.1. Exact commands for each OS are on this page.

Q: Is CVE-2026-85925 being exploited?

CVE-2026-85925 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-85925 affect?

CVE-2026-85925 affects azure-keyvault-administration, azure-keyvault-certificates, azure-keyvault-keys. Severity is high (CVSS 8.2). Improper restriction of communication channel to intended endpoints in Azure Key Vault allows an authorized attacker to elevate privileges over a network.

Q: How urgent is CVE-2026-85925?

Priority 45/100. High severity; On your watchlist

This month

HIGH 8.2WATCHLISTUPGRADEUPGRADEUPGRADE

CVE-2026-85925 is a high-severity flaw (CVSS 8.2) affecting azure-keyvault-administration, azure-keyvault-certificates, azure-keyvault-keys. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Improper restriction of communication channel to intended endpoints in Azure Key Vault allows an authorized attacker to elevate privileges over a network.

Why this priority

High severity
On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score	8.2 (High)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.5% (top 56%)
CISA exploited list	No
Weakness	CWE-923
Published	2026-10-13
Last modified	2026-10-16

Publisher (CNA): Microsoft Corporation · Vendor: microsoft

Last updated 2026-10-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-10-13 19:21 UTCPublished CVE record published
2026-10-16 17:51 UTCUpdated Record last modified

microsoft azure-keyvault-administration UPGRADE

Affected: < 4.8.1

Fixed in: 4.8.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy azure-keyvault-administration || rpm -q azure-keyvault-administration || azure-keyvault-administration --version

2. UPGRADE to 4.8.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade azure-keyvault-administration

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade azure-keyvault-administration

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

microsoft azure-keyvault-certificates UPGRADE

Affected: < 4.9.1

Fixed in: 4.9.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy azure-keyvault-certificates || rpm -q azure-keyvault-certificates || azure-keyvault-certificates --version

2. UPGRADE to 4.9.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade azure-keyvault-certificates

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade azure-keyvault-certificates

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

microsoft azure-keyvault-keys UPGRADE

Affected: < 4.10.1

Fixed in: 4.10.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy azure-keyvault-keys || rpm -q azure-keyvault-keys || azure-keyvault-keys --version

2. UPGRADE to 4.10.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade azure-keyvault-keys

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade azure-keyvault-keys

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

microsoft azure-keyvault-secrets UPGRADE

Affected: < 4.11.1

Fixed in: 4.11.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy azure-keyvault-secrets || rpm -q azure-keyvault-secrets || azure-keyvault-secrets --version

2. UPGRADE to 4.11.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade azure-keyvault-secrets

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade azure-keyvault-secrets

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · 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-85925?

azure-keyvault-administration: upgrade to 4.8.1; azure-keyvault-certificates: upgrade to 4.9.1; azure-keyvault-keys: upgrade to 4.10.1. Exact commands for each OS are on this page.

Is CVE-2026-85925 being exploited?

CVE-2026-85925 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-85925 affect?

CVE-2026-85925 affects azure-keyvault-administration, azure-keyvault-certificates, azure-keyvault-keys. Severity is high (CVSS 8.2). Improper restriction of communication channel to intended endpoints in Azure Key Vault allows an authorized attacker to elevate privileges over a network.

How urgent is CVE-2026-85925?

Priority 45/100. High severity; On your watchlist

Software pages

Azure vulnerabilities · HashiCorp Vault vulnerabilities

Related CVEs

CVE-2026-85922 HIGH 7.4 UPGRADE UPGRADE Weak authentication in Azure Key Vault allows an unauthorized attacker to bypass a security feature over a net

References

← Back to latest CVEs