Microsoft security update for CVE-2026-81870 — azl3
🔗 CVE IDs covered (1)
📋 Microsoft's advisory
EchelonGraph does not copy Microsoft's advisory page: its FAQ and remediation text are not shown here. Read the advisory on https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-81870. This page also shows what EchelonGraph holds for CVE-2026-81870, with the description from its CVE record, which the CVE Numbering Authority that assigned the CVE wrote: for a CVE Microsoft assigned, often in the words of Microsoft's own advisory.
🎯 Affected products41
- azl3 azurelinux-image-tools 1.6.0-2 on Azure Linux 3.0
- azl3 azurelinux-image-tools 1.6.0-3 on Azure Linux 3.0
- azl3 cert-manager 1.12.15-12 on Azure Linux 3.0
- azl3 cert-manager 1.12.15-14 on Azure Linux 3.0
- azl3 cloud-provider-kubevirt 0.5.1-10 on Azure Linux 3.0
- azl3 cloud-provider-kubevirt 0.5.1-7 on Azure Linux 3.0
- azl3 cloud-provider-kubevirt 0.5.1-9 on Azure Linux 3.0
- azl3 containerd2 2.2.4-8 on Azure Linux 3.0
- azl3 containerd2 2.3.4-1 on Azure Linux 3.0
- azl3 containerd2 2.3.7-1 on Azure Linux 3.0
- azl3 cri-tools 1.32.0-10 on Azure Linux 3.0
- azl3 cri-tools 1.32.0-7 on Azure Linux 3.0
- azl3 cri-tools 1.32.0-8 on Azure Linux 3.0
- azl3 docker-buildx 0.14.0-16 on Azure Linux 3.0
- azl3 docker-buildx 0.14.0-17 on Azure Linux 3.0
- azl3 docker-compose 2.27.0-13 on Azure Linux 3.0
- azl3 docker-compose 2.27.0-14 on Azure Linux 3.0
- azl3 etcd 3.5.33-1 on Azure Linux 3.0
- azl3 flannel 0.24.2-31 on Azure Linux 3.0
- azl3 flannel 0.24.2-32 on Azure Linux 3.0
- azl3 kata-containers 3.32.0.kata0-5 on Azure Linux 3.0
- azl3 kata-containers 4.1.0.kata0-1 on Azure Linux 3.0
- azl3 kata-containers 4.1.0.kata1-2 on Azure Linux 3.0
- azl3 kata-containers-cc 3.15.0.aks0-20 on Azure Linux 3.0
- azl3 kata-containers-cc 3.15.0.aks0-21 on Azure Linux 3.0
- azl3 kata-containers-cc 3.15.0.aks0-23 on Azure Linux 3.0
- azl3 keda 2.14.1-18 on Azure Linux 3.0
- azl3 keda 2.14.1-19 on Azure Linux 3.0
- azl3 kube-vip-cloud-provider 0.0.10-10 on Azure Linux 3.0
- azl3 kube-vip-cloud-provider 0.0.10-8 on Azure Linux 3.0
- +11 more not shown
✅ Updates Microsoft lists: 14 updates
14 rows: one per KB article or update, update type and fixed build. Their details are on Microsoft's advisory.
| KB article | Update | Fixed build |
|---|---|---|
| — | Security Update | — |
| — | Security Update | 3.5.35-1 |
| — | Security Update | — |
| — | Security Update | 1.7.0-2 |
| — | Security Update | 2.27.0-16 |
| — | Security Update | 0.24.2-34 |
| — | Security Update | 3.15.0.aks0-23 |
| — | Security Update | 1.12.15-15 |
| — | Security Update | 2.4.0-1 |
| — | Security Update | 0.14.0-19 |
| — | Security Update | 4.1.0.kata1-2 |
| — | Security Update | 0.0.10-11 |
| — | Security Update | 1.7.7-19 |
| — | Security Update | 2.3.7-1 |
🧭 EchelonGraph on CVE-2026-81870
- EchelonGraph score
- 2.0 LOW
- CISA KEV
- Not listed
- Fix status
- A fix is available — apply it.
Description from the CVE record (CVE.org), as published by its numbering authority
OpenTelemetry-Go is the Go implementation of OpenTelemetry. From version 1.5.0 to 1.44.0, sdk/trace.NewTracerProvider emits a TracerProvider created internal Info-level diagnostic event whose MarshalLog implementations recursively include span processor, exporter, and client configuration. Applications that call otel.SetLogger to enable OpenTelemetry internal Info logging can therefore record OTLP gRPC and HTTP collector endpoints, the OTLP HTTP Insecure flag, and complete Zipkin collector URLs. A person or system with access to those logs can learn internal collector topology and can recover credentials or tokens embedded in Zipkin URL user information or query strings. The default OpenTelemetry logger does not emit the event, and this path does not log OTLP authentication headers, TLS key material, or span payloads. This issue is fixed in version 1.45.0.
Published by GitHub, Inc., the CVE Numbering Authority that assigned CVE-2026-81870, in its CVE record at CVE.org; reused under the CVE Program's Terms of Use (its licence and MITRE's copyright notice are in our Terms of Service).