CVE-2022-37968 json
Azure Arc-enabled Kubernetes cluster Connect Elevation of Privilege Vulnerability
published 2022-10-11 4 y ago modified 2026-06-17 4 mo ago also EUVD-2022-40575
- cvss
- 10.0
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.0%
- EPSS 3.0% chance of exploitation in 30 days, percentile 87%
- public exploits
- 0
- none known
Summary
Microsoft has identified a vulnerability affecting the cluster connect feature of Azure Arc-enabled Kubernetes clusters. This vulnerability could allow an unauthenticated user to elevate their privileges and potentially gain administrative control over the Kubernetes cluster. Additionally, because Azure Stack Edge allows customers to deploy Kubernetes workloads on their devices via Azure Arc, Azure Stack Edge devices are also vulnerable to this vulnerability.
Patch / fix
- Microsoft Azure Arc-enabled Kubernetes cluster 1.8.11 1.8.11
- Microsoft Azure Arc-enabled Kubernetes cluster 1.7.18 1.7.18
- Microsoft Azure Arc-enabled Kubernetes cluster 1.5.8 1.5.8
- Microsoft Azure Arc-enabled Kubernetes cluster 1.6.19 1.6.19
- Microsoft Azure Stack Edge 2.2.2088.5593
Exploit prediction
2.98% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 10.0 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H/E:U/RL:O/RC:C |
| CNA | 3.1 | 10.0 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H |
Affected products
- Microsoft Azure Arc-enabled Kubernetes cluster 1.8.11
- Microsoft Azure Arc-enabled Kubernetes cluster 1.7.18
- Microsoft Azure Arc-enabled Kubernetes cluster 1.5.8
- Microsoft Azure Arc-enabled Kubernetes cluster 1.6.19
- Microsoft Azure Stack Edge
References
-
portal.msrc.microsoft.com
/en-US/security-guidance/advisory/CVE-2022-37968
patch, vendor-advisory
-
msrc.microsoft.com
/update-guide/vulnerability/CVE-2022-37968
vendor-advisory
Sources
- CVE List CVE-2022-37968
- NVD CVE-2022-37968
Fencer Vulns 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.