Microsoft's Azure Linux project published release 3.0.20261105-3.0 on GitHub on Nov. 7. It is a single release with a very long changelog. The Register counted more than 470 CVE references in the release notes. It also noted that some of those references repeat across packages, so the number of distinct vulnerabilities is lower than the headline figure. The fixes cover the parts of a modern cloud host that matter most: the Linux kernel, OpenSSL, curl, Kubernetes, Docker, QEMU, KubeVirt, containerd and Docker Compose.
The most important change for most admins is not the size of the release. It is a certificate trust change. The release removes or distrusts root certificates that could validate compromised intermediate certificates issued by eMudhra, which is tracked as CVE-2026-114406. It also adds code to the Go and Python stacks that rejects those intermediates outright.
A note on naming: The Register's story calls the release "Azure Linux 3.0.2022". The tag on the project's GitHub releases page is 3.0.20261105, and that is the identifier to use when you check your own hosts.
What is Azure Linux, and why does a bulk release matter?
Azure Linux is Microsoft's own Linux distribution, formerly known as CBL-Mariner, developed primarily for its cloud infrastructure and services. That helps explain why so much of this changelog is container and virtualization tooling. Kubernetes, containerd, Docker and Docker Compose run workloads. QEMU and KubeVirt run virtual machines, including VMs managed through Kubernetes. OpenSSL and curl handle encrypted connections and data transfer for almost everything else.
Large rollup releases like this one change how you test. Patching one package at a time lets you isolate a regression. When a release touches the kernel, the TLS library and the container runtime together, you need to test the whole stack before you put it into production.
This release moves the generic kernel to kernel-6.6.161.1-1. The release notes list the CVE references for each package. The source material does not single out any one of them as actively exploited.
The eMudhra problem, in plain English
CVE-2026-114406 was published on Oct. 21, 2026. Red Hat is the source of the record, and the NVD entry still shows it as awaiting analysis. The record describes a problem with the system certificate authority store in Red Hat products, distributed through ca-certificates RPM packages.
Some background: when your server opens an HTTPS connection, it checks the remote certificate against a list of trusted root certificate authorities (CAs) kept on the machine. Roots seldom sign website certificates directly. They sign intermediate certificates, and those intermediates sign the certificates that websites present. Software that trusts a root therefore trusts every intermediate below it.
According to the NVD record, the system store included roots of authorities that signed intermediate CA certificates issued by eMudhra with weak private keys. The record says a man-in-the-middle attacker could use this flaw to issue certificates for arbitrary host names, signed by the weak intermediates, and that a TLS client using the system store would treat them as trusted and connect to malicious sites. In practice, that means an attacker positioned on the network could impersonate an HTTPS site, API endpoint or package mirror without the client raising a warning.
The NVD record also explains the fix. It says specific intermediate certificates cannot be distrusted in all clients that use the system CA store, so the root CA certificates of the authorities that signed the weak intermediates are being removed. This is a blunt approach, but it works in every client that reads the system store.
How Azure Linux implemented it
The GitHub release notes describe a layered response:
- Root removal and distrust. The notes say root certificates that could validate the compromised eMudhra intermediates were removed or distrusted. They also list ca-certificates 1:3.0.0-19, described as a refresh of Microsoft trusted root certificates.
- Explicit distrust in NSS. nss 3.96.1-4 explicitly distrusts the affected root certificates. NSS is the Network Security Services library used by Firefox-derived software and some system tools.
- Go rejects the intermediates directly. golang 1.27.3-1 changes
crypto/x509to reject the compromised intermediate certificates. That change is tracked as CVE-2026-111943. Fixing the language toolchain as well as the trust store matters because a program can carry certificate-handling logic of its own. - Python rejects them too. python3 3.12.16-1 rejects the compromised eMudhra intermediates and removes the affected roots from the ensurepip wheel. python-pip 24.2-11 removes the affected roots from its bundled certifi trust store, and grpc 1.62.3-4 removes affected root certificates and preserves SSL.com TLS trust.
- SSL.com TLS trust kept. The project says it preserved SSL.com trust for TLS where needed. The Register suggests this avoids fixing one certificate problem by creating another, since a root cleanup could otherwise break connections that rely on legitimate certificates.
The layering shows why the work has to happen in several places. Removing a root from the system store protects clients that read the system store. It does nothing for software that carries its own trust data or verifies certificates its own way, which is why the release also touches NSS, Go, Python and individual packages with bundled root lists.
Is AI behind the flood?
A changelog with more than 470 CVE references raises an obvious question: is AI-assisted bug hunting driving the volume? The Register describes the release as arriving amid an AI-fueled surge in vulnerability discovery, and says Microsoft has not said whether AI-assisted research contributed to the vulnerabilities addressed in this release. The same article cites Linus Torvalds saying there may be signs the flood is easing in some corners of the kernel: fixes are now arriving faster than new bug reports in the eBPF subsystem, although he noted that most other areas have not reached that point. That comment is about the Linux kernel in general, not about Azure Linux. Nothing in the sources links this release to AI-found bugs.
For defenders, the cause matters less than the result. Distributions are shipping larger, denser updates, and patch pipelines need to handle that volume without people having to review every CVE line by hand.
What It Means for Defenders
Who is affected: anyone running Azure Linux 3.0 hosts, container images built on Azure Linux, or Kubernetes nodes that use it. The certificate problem, CVE-2026-114406, is not specific to Azure Linux. The NVD record describes it as affecting the system CA store in Red Hat products shipped through ca-certificates packages, and Azure Linux's own notes reference the same incident. If you run other distributions, watch for your vendor's version of the same root removal.
What to patch: move to Azure Linux release 3.0.20261105. The package versions named in the release notes are:
- Kernel: kernel-6.6.161.1-1 (a kernel update takes effect only after a reboot)
- ca-certificates 1:3.0.0-19
- nss 3.96.1-4
- golang 1.27.3-1 (CVE-2026-111943)
- python3 3.12.16-1, python-pip 24.2-11 and grpc 1.62.3-4
The same release also contains the OpenSSL, curl, Kubernetes, Docker, containerd, Docker Compose, QEMU and KubeVirt fixes.
What to check:
- Rebuild Go binaries. Updating the Go toolchain does not change binaries that were compiled earlier. A Go service built with an older toolchain keeps the old
crypto/x509behaviour until you recompile it with golang 1.27.3-1 or later and redeploy it. The same applies to container images that bundle their own Go programs. - Rebuild container images. Images built on an older Azure Linux base layer still carry the old trust store and libraries. Updating the host does not fix them.
- Look for bundled trust stores. Applications that ship their own CA bundle do not read the system store and will not pick up this change. The release notes show several packages, such as the Snowflake bundle in influxdb, needing their own root removals. Find such bundles in your estate and check what they trust.
- Watch for TLS breakage. Removing roots can break connections to services whose certificates chain to the removed authorities. SSL.com TLS trust was preserved, but test internal and partner endpoints before a fleet-wide rollout.
- Stage the rollout. A release that touches the kernel, OpenSSL and the container runtime together deserves a canary node pool before general deployment.
Do you need to rotate anything? The sources do not say any eMudhra-related certificate was used in a real attack, and they do not tell organizations to rotate their own keys. If you have certificates issued under the affected eMudhra hierarchy, ask your CA whether they will still be trusted once these roots are removed.
For CMMC and federal contractors: keep a record of when this update was applied across your Azure Linux assets. Documented, timely patching of a trust store change like this one fits the system and information integrity practices assessors tend to ask about, though none of the sources address CMMC directly.