29.9.2
Release date |
Name |
Upstream release |
|---|---|---|
2026-NOV-18 |
MCR 29.9.2 |
Moby 29.9.2 and Docker CLI 29.9.2 |
Important
Due to the upgrade of containerd from 1.x to 2.x, before you upgrade from a previous MCR major release to MCR 29.9.2 you must upgrade
containerd.iobefore you upgradedocker-ee. In the event that you have upgraded both components at the same time and some of the containers that should have restarted remain stopped, you can get them running again by restarting MCR with the systemctl restart docker command.Upgrading from MCR 29.6.1.x or earlier: Compose recreates containers once.
The bundled Compose plugin moves from the 5.5 line to 5.6, bringing the upstream 5.2 through 5.5 feature set. Compose 5.5 changes how it records image identity, so the first
docker compose upafter upgrade recreates containers once per project. On daemons that use the containerd image store (driver typeio.containerd.snapshotter.v1indocker infooutput), Compose recreates every container in every project. On overlay2 and other graphdrivers, Compose recreates only the containers of services that mount atype: imagevolume. Before you upgrade, check the image store of each daemon and exercise the upgrade in a staging environment. If a project cannot absorb the recreation, schedule the upgrade for a maintenance window. Compose 5.5 also honors thedaily,weekly, andevery_<n>pull_policyrefresh windows. Review any external workaround for the previous always-pull behavior, as it may now be redundant or conflict with the Compose file.
Highlights
Enhancement |
Detail |
|---|---|
MCR built with Go 1.26.10. |
Docker Compose plugin upgraded to 5.6.0, which adds partial support for Compose jobs. |
Changelog
MCR 29.9.2 comprises the Moby 29.9.2 and Docker CLI 29.9.2 upstream releases. In addition, changes are included for the interceding upstream 29.9.1, 29.9.0, 29.8.2, and 29.8.1 releases, for which there were no MCR releases.
Changes specific to MCR
MCR is built with Go 1.26.10, which covers the engine, the Docker CLI, containerd, runc, RootlessKit, gVisor (
runsc-ee), and the Compose plugin.containerd moves from 2.3.4 to 2.4.2. See Changes from upstream.
Important
containerd 2.4 no longer honors the following deprecated configuration options. Before you upgrade, check any customized
/etc/containerd/config.tomlfor these options and move each setting to its replacement:enable_cdiin the CRI runtime configuration. Remove the option; CDI is always enabled.bin_dirin the CRI CNI configuration. Usebin_dirs.endpoint,protocolandinsecurein the OTLP tracing processor configuration. Use the standard OpenTelemetry environment variables.service_nameandsampling_ratioin the internal tracing configuration. Use the standard OpenTelemetry environment variables.
The bundled Compose plugin moves to 5.6.0, which adds partial support for Compose jobs. Run a job manually with
docker compose run <job>.docker compose uprejects scheduled jobs.rootlesskit-eemoves to RootlessKit 3.3.0. With thebuiltinport driver, RootlessKit prefers nftables over iptables for source-IP-transparent port forwarding, and falls back to iptables when nft is not installed.runsc-eeis rebuilt from gVisor release 20260831.0.Fixes backported ahead of upstream:
Swarm: a task can reach a service’s published port through its own node’s address when a host firewall, such as ufw, drops unsolicited incoming traffic (moby/moby#54006).
firewalld: the daemon restores its iptables rules when firewalld stops, and starts using firewalld when firewalld starts after the daemon (moby/moby#54012).
Changes from upstream
The upstream pull requests detailed in the sections that follow are those that pertain to the MCR product. For the complete list of changes and pull requests upstream, refer to the GitHub milestones.
Security
MCR 29.9.2 release mitigates several CVEs that affect MCR container images. Click the dropdown link below for comprehensive details.
CVEs Resolved
CVE |
Image mitigated |
Problem details from upstream |
|---|---|---|
|
HTTP/2 servers could end up crashing due to inadvertently modifying its HPACK encoder concurrently. This happens because the server modifies the HPACK encoder from two goroutines without synchronization: one uses the encoder to encode a HEADERS frame as part of a response sent to a client and the other modifies the encoder’s table size when handling a SETTINGS frame containing SETTINGS_HEADER_TABLE_SIZE that a client sends. A malicious client can repeatedly send a request while changing the header table size to crash the server. |
|
|
Multiple ECH outer extension references are not permitted under RFC 9849; previously, a client could send a well-crafted packet that could trigger memory exhaustion in the server process by specifying multiple references. We now reject these as malformed and curb the memory amplification vector as a result. |
|
|
Parsing a multipart form can bypass memory limits and read an arbitrarily long line into memory when the remaining limit at the start of a part is less than 400 bytes. |
|
|
When an HTTP server handler sends a 2xx response to an HTTP/1 CONNECT request and returns without hijacking the connection, the server improperly continues to read and serve requests from the connection. Since a 2xx response to an HTTP/1 CONNECT converts the connection into a tunnel, the server should not treat the connection as continuing to contain HTTP. The impact of this misbehavior is mostly limited to potential request smuggling, where an intermediate proxy considers the data on the connection to be tunneled and the server considers it to be HTTP. |
|
|
gRPC-Go is the Go language implementation of gRPC. Prior to 1.82.2 and 1.83.2, servers created with xds.NewGRPCServer() allow internal/transport/http2_server.go to accept an RPC containing neither the :authority header nor the Host header, while RouteAndProcess in internal/xds/server/routing.go assumes that an authority value exists and indexes the empty slice. A remote client that can complete transport connection establishment can trigger an index-out-of-bounds panic that is not recovered by the per-RPC goroutine and terminates the entire server process. In insecure or ordinary TLS deployments the request can be unauthenticated, while strict mTLS or ALTS deployments require valid transport credentials before the malformed RPC can reach the interceptor. This issue is fixed in versions 1.82.2 and 1.83.2. |
|
|
A malicious HTTP/2 peer can cause excessive CPU consumption in the client or server by opening a large number of streams and then sending many small SETTINGS frames containing SETTINGS_INITIAL_WINDOW_SIZE values. |
|
|
When parsing a Range header containing a large number of small ranges, FileServer(FS), ServeContent, and ServeFile(FS) can consume an excessive amount of CPU. |
|
|
The HTTP/2 server can refund connection-level flow control twice for the same data: Once when a client resets a stream (refunding data for any sent-but-unread portion of the stream), and again when a request handler reads the buffered data. A malicious client can exploit this to bypass the configured connection-level flow control limit (MaxReceiveBufferPerConnection). Total buffered data is still limited by the concurrent stream limit and stream-level flow control. |
|
|
Previously, a channel registered in the mux’s chanList is not usable until it is established. A malicious peer was able flood the channel’s incomingRequests, deadlocking the entire connection. Now, we add an atomic established state, set when a channel becomes usable. Until such a time, handlePacket drops every packet other than the open confirmation/failure, without blocking and without tearing down the connection. |
|
|
Historically, we have been rather lax about malformed framing-related headers in our HTTP/2 implementation, as they cannot interfere with HTTP/2 framing. However, this makes it possible for our HTTP/2 implementation to forward responses containing such headers to an HTTP/1 client when acting as a reverse proxy. If the HTTP/1 client also does not behave strictly enough, this can result in response smuggling. |
|
|
When “Trailer” headers are sent by a client, the HTTP server internally uses the header values to populate the Request.Trailer map passed to the server handler. Because Request.Trailer is a map, each entry incurs memory overhead. For HTTP/2 servers, a malicious client can exploit this by sending a “Trailer” header that declares a large number of fields, causing the server to allocate a disproportionate amount of memory while bypassing Server.MaxHeaderValueCount and Server.MaxHeaderBytes limits. This exploit is not applicable for HTTP/1 servers, which do not support multiplexing a large number of requests over one TCP connection, and whose Server.MaxHeaderBytes are calculated differently. |
|
|
compress provides various compression algorithms. Prior to version 1.18.7, a signed integer overflow vulnerability in s2.NewDict() allows an attacker to bypass repeat index validation by supplying a dictionary with a uvarint-encoded repeat value exceeding MaxInt64. When Dict.Encode() is subsequently called, the overflowed negative repeat value causes an out-of-bounds memory access via unsafe.Pointer arithmetic, crashing the process with SIGSEGV. This issue has been patched in version 1.18.7. |
|
|
When http.Transport sends an HTTP/1 CONNECT request with a non-empty Request.Body, it writes the body directly to the connection without framing after the request headers. If the server rejects the CONNECT request with a non-2xx keep-alive response, Transport returns the connection to the idle pool. Because CONNECT requests do not have a request body, the server may interpret the trailing body bytes as a subsequent pipelined HTTP/1.1 request on the connection, leaving the pooled connection desynchronized and causing the next caller that reuses it to read the response to the injected request. In reverse proxies (including httputil.ReverseProxy) that forward CONNECT requests through a shared Transport, this can lead to cross-user response poisoning. |
|
|
On Windows, when the target of Root.Mkdir or Root.MkdirAll is a junction pointing to an empty location, the operation can create a directory at the junction target even when that target is located outside the root. This only applies to operations where the last path component is a junction (path/to/junction, but not path/junction/target). |
|
|
Previously, after a channel has been established, a malicious peer could send crafted messages that would deadlock the entire connection. Now, we handle all RFC 4254 channel messages; global requests are handled explicitly. Then, treat all other messages as a protocol error and tear the connection down instead of buffering and blocking. |
|
|
Moby is an open source container framework. In Docker Engine prior to version 29.5.1, Docker Daemon versions 28.5.2 and prior, and Moby Daemon prior to version 2.0.0-beta.14, a race condition during docker cp mount setup allows a malicious container to redirect a bind mount target to an arbitrary host path, potentially overwriting host files or causing denial of service. This issue has been patched in Docker Engine version 29.5.1 and Moby Daemon version 2.0.0-beta.14. |
|
|
Moby is an open source container framework. In versions prior to 29.5.1 and in moby/moby v2 prior to v2.0.0-beta.14, when a compressed archive is uploaded to a container via PUT /containers/{id}/archive or piped through docker cp -, the daemon resolves decompression binaries (such as xz or unpigz) from the container’s filesystem rather than the host’s due to incorrect ordering of operations. A malicious container image containing a trojanized decompression binary can achieve arbitrary code execution with full daemon privileges, including host root UID and unrestricted capabilities, when a user uploads a compressed (xz or gzip) archive into that container. This issue is fixed in Docker Engine 29.5.1 and moby/moby v2.0.0-beta.14. Workarounds include only running containers from trusted images, using authorization plugins to restrict access to the PUT /containers/{id}/archive endpoint, and avoiding piping compressed archives into containers created from untrusted images |
GitHub milestones
The GitHub milestones offer full detail on the pull requests and changes as they correlate to the upstream Moby 29.9.2, 29.9.1, 29.9.0, 29.8.2, and 29.8.1 releases.
Major component versions
Note
MCR component versions are referenced from the latest builds in the
test-29.9.2 branch pool (Ubuntu 24.04 / noble, amd64).
Release-candidate (rc) and technology-preview (tp) suffixes have
been stripped.
Version detail for the major components that comprise MCR 29.6.1 is presented in the table below:
Component |
Upstream Version |
Mirantis Version |
|---|---|---|
29.9.2m1 |
||
29.9.2m1 |
||
2.4.2m1 |
||
1.4.3m1 |
||
– |
||
– |
||
0.37.2-m.1 |
||
Go runtime |
– |
|
0.34.0 (vendored in Moby 29.9.2) |
– |
|
3.3.0m1 |
||
gVisor |
20260831.0m2 |
|
Docker Compose CLI plugin |
5.6.0 |
5.6.0m1 |
Platform test detail
Platform |
Kernel tested |
|---|---|
Oracle Linux 9.8 |
5.14.0-687.66.1.el9_8.x86_64 |
RHEL 10.2 |
6.12.0-264.16.1.el10_3.x86_64 |
RHEL 10.0 |
6.12.0-264.16.1.el10_3.x86_64 |
RHEL 9.8 |
5.14.0-687.59.1.el9_8.x86_64 |
RHEL 8.10 |
4.18.0-553.172.1.el8_10.x86_64 |
Rocky 10.1 |
6.12.0-211.74.1.el10_2.x86_64 |
Rocky 8.10 |
4.18.0-553.137.1.el8_10.x86_64 |
SLES15 SP7 |
6.4.0-150700.53.90-default |
Ubuntu 26.04 |
7.0.0-1016-aws |
Ubuntu 24.04 |
7.0.0-1014-aws |
Ubuntu 22.04 |
6.8.0-1069-aws |
Windows 2025 Core |
10.0 26100 |
Windows 2022 Core |
10.0 20348 |