CVE-2026-41567
Docker: `PUT /containers/{id}/archive` executes container binary on the host
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
Attack profile
How easy it is to exploit
- Attack vector
- Local
- Complexity
- High
- Privileges needed
- Low
- User interaction
- Required
What an attacker can affect
- Confidentiality
- High
- Integrity
- High
- Availability
- None
Exploit likelihood
What each source reports
CVE List Score used
7.2
Docker: `PUT /containers/{id}/archive` executes container binary on the host
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
- Record
CVE-2026-41567- CVSS 3.1
- 7.2 High
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N - CVSS 3.1
- 7.5 High
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H - Weakness
- CWE-427, CWE-427
- Updated
- 2026-11-02
EUVDEUVD-2026-34779
7.5
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
- Record
EUVD-2026-34779- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H - Updated
- 2026-11-02
GitHub AdvisoriesGHSA-x86f-5xw2-fm2r
7.2
Docker: `PUT /containers/{id}/archive` executes container binary on the host
Summary
When a user uploads a compressed archive into a container, a malicious image can execute arbitrary code with daemon (host root) privileges.
Details
When handling PUT /containers/{id}/archive requests with compressed archives, the daemon decompresses them using external system binaries. Due to incorrect ordering of operations, these binaries are resolved from the container's filesystem rather than the host's. A container image that includes a trojanized decompression binary can achieve code execution as the daemon process whenever a compressed archive is uploaded to that container.
The executed binary runs with the daemon's full privileges, including host root UID and unrestricted capabilities.
Impact
Arbitrary code execution as host root, crossing the container-to-host trust boundary.
Conditions for exploitation
- A user must run a container from a malicious image that contains a trojanized decompression binary.
- The user must then upload a compressed archive (xz or gzip) into that container, either by piping a compressed archive via
docker cp -or by calling thePUT /containers/{id}/archiveAPI directly with compressed content.
Not affected
Standard docker cp usage is not affected, because the CLI sends uncompressed tar by default:
docker cp ./file.txt mycontainer:/file.txt
This can only be exploited when explicitly passing a xz or gzip-compressed archive to docker cp or the PUT /containers/{id}/archive API, for example:
cat archive.tar.xz | docker cp - mycontainer:/dir
Decompression formats using pure Go implementations (bzip2, zstd, and gzip when the container image does not contain an unpigz binary) are also not affected.
Workarounds
- Only run containers from trusted images.
- Use authorization plugins to limit access to the
PUT /containers/{id}/archiveendpoint. - Avoid piping compressed archives into containers created from untrusted images.
- Record
GHSA-x86f-5xw2-fm2r- CVSS 3.1
- 7.2 High
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N - Weakness
- CWE-427
- Updated
- 2026-11-02
NVD
7.2
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
- Record
CVE-2026-41567- CVSS 3.1
- 7.2 High
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N - CVSS 3.1
- 7.5 High
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H - Weakness
- CWE-427
- Updated
- 2026-11-02
OSVALPINE-CVE-2026-41567
7.2
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
- Record
ALPINE-CVE-2026-41567- CVSS 3.1
- 7.2 High
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N - Updated
- 2026-11-03
OSVBELL-CVE-2026-41567
7.2
- Record
BELL-CVE-2026-41567- CVSS 3.1
- 7.2 High
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N - Updated
- 2026-11-03
Show 22 moreShow less
OSV
7.2
Docker: `PUT /containers/{id}/archive` executes container binary on the host
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
- Record
CVE-2026-41567- CVSS 3.1
- 7.2 High
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N - Weakness
- CWE-427
- Updated
- 2026-11-02
OSVDEBIAN-CVE-2026-41567
7.2
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
- Record
DEBIAN-CVE-2026-41567- CVSS 3.1
- 7.2 High
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N - Updated
- 2026-11-02
OSVGHSA-x86f-5xw2-fm2r
7.2
Docker: `PUT /containers/{id}/archive` executes container binary on the host
Summary
When a user uploads a compressed archive into a container, a malicious image can execute arbitrary code with daemon (host root) privileges.
Details
When handling PUT /containers/{id}/archive requests with compressed archives, the daemon decompresses them using external system binaries. Due to incorrect ordering of operations, these binaries are resolved from the container's filesystem rather than the host's. A container image that includes a trojanized decompression binary can achieve code execution as the daemon process whenever a compressed archive is uploaded to that container.
The executed binary runs with the daemon's full privileges, including host root UID and unrestricted capabilities.
Impact
Arbitrary code execution as host root, crossing the container-to-host trust boundary.
Conditions for exploitation
- A user must run a container from a malicious image that contains a trojanized decompression binary.
- The user must then upload a compressed archive (xz or gzip) into that container, either by piping a compressed archive via
docker cp -or by calling thePUT /containers/{id}/archiveAPI directly with compressed content.
Not affected
Standard docker cp usage is not affected, because the CLI sends uncompressed tar by default:
docker cp ./file.txt mycontainer:/file.txt
This can only be exploited when explicitly passing a xz or gzip-compressed archive to docker cp or the PUT /containers/{id}/archive API, for example:
cat archive.tar.xz | docker cp - mycontainer:/dir
Decompression formats using pure Go implementations (bzip2, zstd, and gzip when the container image does not contain an unpigz binary) are also not affected.
Workarounds
- Only run containers from trusted images.
- Use authorization plugins to limit access to the
PUT /containers/{id}/archiveendpoint. - Avoid piping compressed archives into containers created from untrusted images.
- Record
GHSA-x86f-5xw2-fm2r- CVSS 3.1
- 7.2 High
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N - Weakness
- CWE-427
- Updated
- 2026-11-02
OSVROOT-APP-GOBINARY-CVE-2026-41567
7.2
CVE-2026-41567 in github.com/docker/docker - Patched by Root
Root has patched CVE-2026-41567 in the github.com/docker/docker package for Root:Go. Multiple fixed versions available.
- Record
ROOT-APP-GOBINARY-CVE-2026-41567- CVSS 3.1
- 7.2 High
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N - Updated
- 2026-11-02
OSVUBUNTU-CVE-2026-41567
7.2
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
- Record
UBUNTU-CVE-2026-41567- CVSS 3.1
- 7.2 High
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N - CVSS 3.1
- 7.5 High
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H - Updated
- 2026-11-02
OSVGO-2026-5746 No score
Docker: 'PUT /containers/{id}/archive' executes container binary on the host in github.com/docker/docker
The Docker daemon's implementation of the "PUT /containers/{id}/archive" endpoint executes a container binary on the host when extracting an archive to a container. On Unix-like systems, this can be exploited if an attacker can control the container's filesystem or the archive being extracted, potentially leading to privilege escalation or host compromise.
The affected code is located in the daemon package, specifically in the containerExtractToDir method of the Daemon struct. This package is part of the Moby daemon's core and is not intended for external use as a library.
- Record
GO-2026-5746- Updated
- 2026-11-02
OSVopenSUSE-SU-2026:11075-1 No score
docker-stable-24.0.9_ce-18.1 on GA media
These are all security issues fixed in the docker-stable-24.0.9_ce-18.1 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2026:11075-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2026:11144-1 No score
docker-29.4.0_ce-40.1 on GA media
These are all security issues fixed in the docker-29.4.0_ce-40.1 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2026:11144-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2026:21060-1 No score
Security update for docker
This update for docker fixes the following issues
- CVE-2026-33814: golang.org/x/net/http2: infinite loop in HTTP/2 transport when given bad SETTINGS_MAX_FRAME_SIZE (bsc#1265782).
- CVE-2026-39821: golang.org/x/net/idna: failure to reject ASCII-only Punycode-encoded labels allows for validation bypass and privilege escalation (bsc#1266625).
- CVE-2026-39984: github.com/sigstore/timestamp-authority/v2/pkg/verification: improper certificate validation can be used to bypass some authorization controls (bsc#1262346).
- CVE-2026-41567: arbitrary code execution with full daemon privileges when a user uploads a compressed archive into that container (bsc#1267827).
- Record
openSUSE-SU-2026:21060-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2026:21205-1 No score
Security update for docker-stable
This update for docker-stable fixes the following issues
- CVE-2026-33186: google.golang.org/grpc: authorization bypass due to improper validation of the HTTP/2 :path pseudo- header (bsc#1260279).
- CVE-2026-33814: golang.org/x/net/http2: infinite loop in HTTP/2 transport when given bad SETTINGS_MAX_FRAME_SIZE (bsc#1265782).
- CVE-2026-33997: moby: docker: github.com/moby/moby: Moby: Privilege validation bypass during plugin installation (bsc#1265907).
- CVE-2026-34040: Authz zero length regression (bsc#1265929).
- CVE-2026-39821: golang.org/x/net/idna: failure to reject ASCII-only Punycode-encoded labels allows for validation bypass and privilege escalation (bsc#1266625).
- CVE-2026-41567: arbitrary code execution with full daemon privileges when a user uploads a compressed archive into that container (bsc#1267827).
- Record
openSUSE-SU-2026:21205-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2026:21483-1 No score
Security update for govulncheck-vulndb
This update for govulncheck-vulndb fixes the following issues:
- Update to version 0.0.20260723T184607 2026-07-23T18:46:07Z (jsc#PED-11136).
Go CVE Numbering Authority IDs added or updated with aliases:
- GO-2026-4730 CVE-2026-33022 GHSA-cv4x-93xx-wgfj
- GO-2026-4761 CVE-2026-33211 GHSA-j5q5-j9gm-2w5c
- GO-2026-5102 CVE-2026-45021 GHSA-3vcp-chfh-f6r2
- GO-2026-5272 CVE-2026-40938 GHSA-94jr-7pqp-xhcq
- GO-2026-5486 CVE-2026-40924 GHSA-m2cx-gpqf-qf74
- GO-2026-5542 CVE-2026-40090 GHSA-pj97-4p9w-gx3q
- GO-2026-5630 CVE-2026-25542 GHSA-rmx9-2pp3-xhcr
- GO-2026-5643 CVE-2026-40923 GHSA-rx35-6rhx-7858
- GO-2026-5675 CVE-2026-41492 GHSA-vvf7-6rmr-m29q
- GO-2026-5711 CVE-2026-40161 GHSA-wjxp-xrpv-xpff
- GO-2026-5746 CVE-2026-41567 GHSA-x86f-5xw2-fm2r
- GO-2026-5749 CVE-2026-41328 GHSA-x92x-px7w-4gx4
- GO-2026-5837 CVE-2026-44840 GHSA-q2m9-6jp9-c6mc
- GO-2026-5929 CVE-2026-44342 GHSA-26v7-h57m-gh9m
- GO-2026-5930 CVE-2026-33655 GHSA-6qcr-qxgr-m7fv
- GO-2026-5933 GHSA-3g4q-2f67-2gvh
- GO-2026-5934 GHSA-59qp-cfj3-rp64
- GO-2026-5935 GHSA-7856-g3gv-9wq8
- GO-2026-5936 CVE-2026-53552 GHSA-26rh-24rg-j3vv
- GO-2026-5937 CVE-2026-53508 GHSA-2jcc-mxv7-p3f9
- GO-2026-5938 CVE-2026-53553 GHSA-4g5x-hcwm-82jw
- GO-2026-5939 CVE-2026-10517 GHSA-698x-9w2p-7vvp
- GO-2026-5940 CVE-2026-53572 GHSA-6w3m-4hhp-775q
- GO-2026-5941 CVE-2026-53487 GHSA-gvhc-wv3v-7pf8
- GO-2026-5942 CVE-2026-46600
- GO-2026-5944 CVE-2026-50197 GHSA-659f-rgp5-w4wf
- GO-2026-5945 CVE-2026-6815 GHSA-rmxx-v9rj-vpvg
- GO-2026-5946 CVE-2026-52831 GHSA-v5px-423j-pf7p
- GO-2026-5947 CVE-2026-53649 GHSA-xqhv-chqm-fhcc
- GO-2026-5948 CVE-2026-50554 GHSA-588f-fvcv-xhvf
- GO-2026-5949 CVE-2026-50553 GHSA-rqrh-8wpv-x7hh
- GO-2026-5950 CVE-2026-53602 GHSA-339v-266x-79xr
- GO-2026-5951 CVE-2026-10219 GHSA-6jm8-4fhr-5w64
- GO-2026-5952 CVE-2026-49834 GHSA-9vcr-p3rj-q5q6
- GO-2026-5953 CVE-2026-9094 GHSA-c9w5-qp6m-m395
- GO-2026-5956 CVE-2026-55252 GHSA-h5g6-xmh4-hc37
- GO-2026-5957 CVE-2026-54158 GHSA-5xfx-xj4h-5p7r
- GO-2026-5958 CVE-2026-54068 GHSA-gcm7-57gf-953c
- GO-2026-5959 CVE-2026-54072 GHSA-h29v-hj44-q8cv
- GO-2026-5961 CVE-2026-54069 GHSA-hvr9-72v2-fff3
- GO-2026-5962 CVE-2026-54088 GHSA-m93h-4hw7-5qcm
- GO-2026-5963 CVE-2026-54067 GHSA-mvjr-vv3c-w4qv
- GO-2026-5964 CVE-2026-54066 GHSA-p4m3-mgmm-c664
- GO-2026-5965 CVE-2026-54070 GHSA-w7cg-whh7-xp28
- GO-2026-5966 CVE-2026-54089 GHSA-xqp3-jq6g-x3qm
- GO-2026-5967 CVE-2026-50551 GHSA-56mp-4f3v-fgj2
- GO-2026-5968 CVE-2026-54174 GHSA-fpg8-7664-jc5q
- GO-2026-5969 GHSA-g936-7jqj-mwv8
- GO-2026-5970 CVE-2026-56852
- GO-2026-5973 CVE-2026-54250 GHSA-jxr7-mqhw-9p98
- GO-2026-5974 CVE-2026-44300 GHSA-wmj8-9953-vff5
- GO-2026-5975 CVE-2026-50018 GHSA-42j2-w334-qxw7
- GO-2026-5976 CVE-2026-50141 GHSA-g7mm-9vx7-jm7h
- GO-2026-5977 CVE-2026-50013 GHSA-qrh4-p6v4-mrfg
- GO-2026-5978 CVE-2026-50125 GHSA-qw5r-ppcg-f8rj
- GO-2026-5979 CVE-2026-50006 GHSA-xrcf-6jh3-ggvx
- GO-2026-5980 CVE-2026-50158 GHSA-2c7f-fxww-6w6c
- GO-2026-5981 GHSA-mqxv-9rm6-w8qc
- GO-2026-5982 GHSA-pqg7-v6wh-3pfp
- GO-2026-5984 CVE-2026-53604 GHSA-2p2f-px33-4vv5
- GO-2026-5985 GHSA-7rx3-5wx3-5v76
- GO-2026-5986 CVE-2026-61699 GHSA-cm26-5974-52h8
- GO-2026-5987 CVE-2026-55513 GHSA-g4x6-jcvr-9m3g
- GO-2026-5988 CVE-2026-54628 GHSA-hwrq-8wxh-q4xv
- GO-2026-5989 CVE-2026-55512 GHSA-m3cx-mwpg-32jg
- GO-2026-5990 CVE-2026-54629 GHSA-mf78-3rpf-r784
- GO-2026-5991 CVE-2026-53603 GHSA-q4vm-pq3q-8wgq
- GO-2026-5992 CVE-2026-61549 GHSA-qf34-295c-26v8
- GO-2026-5996 CVE-2026-54450 GHSA-pph6-vfjv-vpjw
- GO-2026-5997 CVE-2026-54452 GHSA-xgch-x3mx-cm3c
- GO-2026-5998 CVE-2026-54495 GHSA-398h-7f66-3h4p
- GO-2026-5999 CVE-2026-10814 GHSA-jh6h-v6mp-h22v
- GO-2026-6002 CVE-2026-58196 GHSA-pr64-jmmf-jp54
- GO-2026-6003 CVE-2026-53714 GHSA-22xc-xg2r-9j7v
- GO-2026-6004 CVE-2026-52833 GHSA-3v79-m2cg-89ww
- GO-2026-6005 CVE-2026-53715 GHSA-8fv2-88gg-hm7q
- GO-2026-6006 CVE-2026-53716 GHSA-cxpq-8v7q-cg56 *…
- Record
openSUSE-SU-2026:21483-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2026:22158-1 No score
Security update for docker
This update for docker fixes the following issues:
Security issues fixed:
- CVE-2026-33814: golang.org/x/net/http2: infinite loop in HTTP/2 transport when given bad SETTINGS_MAX_FRAME_SIZE (bsc#1265782).
- CVE-2026-39821: golang.org/x/net/idna: failure to reject ASCII-only Punycode-encoded labels allows for validation bypass and privilege escalation (bsc#1266625).
- CVE-2026-39984: github.com/sigstore/timestamp-authority/v2/pkg/verification: improper certificate validation can be used to bypass some authorization controls (bsc#1262346).
- CVE-2026-41567: arbitrary code execution with full daemon privileges when a user uploads a compressed archive into that container (bsc#1267827).
Non security issue fixed:
- SELinux CIL files are not shipped in Docker (bsc#1278193).
Changes for docker:
- Update to Docker 29.7.2. See upstream changelog online at https://docs.docker.com/engine/release-notes/29/#2972 fixes(bsc#1268280, bsc#1268359, bsc#1271209, bsc#1266176)
- Update to buildx 0.36.1. See upstream changelog online at https://github.com/docker/buildx/releases/tag/v0.36.1
- Record
openSUSE-SU-2026:22158-1- Updated
- 2026-11-02
OSVSUSE-SU-2026:22285-1 No score
Security update for docker
This update for docker fixes the following issues
- CVE-2026-33814: golang.org/x/net/http2: infinite loop in HTTP/2 transport when given bad SETTINGS_MAX_FRAME_SIZE (bsc#1265782).
- CVE-2026-39821: golang.org/x/net/idna: failure to reject ASCII-only Punycode-encoded labels allows for validation bypass and privilege escalation (bsc#1266625).
- CVE-2026-39984: github.com/sigstore/timestamp-authority/v2/pkg/verification: improper certificate validation can be used to bypass some authorization controls (bsc#1262346).
- CVE-2026-41567: arbitrary code execution with full daemon privileges when a user uploads a compressed archive into that container (bsc#1267827).
- Record
SUSE-SU-2026:22285-1- Updated
- 2026-11-02
OSVSUSE-SU-2026:22367-1 No score
Security update for docker
This update for docker fixes the following issues
- CVE-2026-33814: golang.org/x/net/http2: infinite loop in HTTP/2 transport when given bad SETTINGS_MAX_FRAME_SIZE (bsc#1265782).
- CVE-2026-39821: golang.org/x/net/idna: failure to reject ASCII-only Punycode-encoded labels allows for validation bypass and privilege escalation (bsc#1266625).
- CVE-2026-39984: github.com/sigstore/timestamp-authority/v2/pkg/verification: improper certificate validation can be used to bypass some authorization controls (bsc#1262346).
- CVE-2026-41567: arbitrary code execution with full daemon privileges when a user uploads a compressed archive into that container (bsc#1267827).
- Record
SUSE-SU-2026:22367-1- Updated
- 2026-11-02
OSVSUSE-SU-2026:22456-1 No score
Security update for docker
This update for docker fixes the following issues
- CVE-2026-33814: golang.org/x/net/http2: infinite loop in HTTP/2 transport when given bad SETTINGS_MAX_FRAME_SIZE (bsc#1265782).
- CVE-2026-39821: golang.org/x/net/idna: failure to reject ASCII-only Punycode-encoded labels allows for validation bypass and privilege escalation (bsc#1266625).
- CVE-2026-39984: github.com/sigstore/timestamp-authority/v2/pkg/verification: improper certificate validation can be used to bypass some authorization controls (bsc#1262346).
- CVE-2026-41567: arbitrary code execution with full daemon privileges when a user uploads a compressed archive into that container (bsc#1267827).
- Record
SUSE-SU-2026:22456-1- Updated
- 2026-11-02
OSVSUSE-SU-2026:22513-1 No score
Security update for docker
This update for docker fixes the following issues
- CVE-2026-33814: golang.org/x/net/http2: infinite loop in HTTP/2 transport when given bad SETTINGS_MAX_FRAME_SIZE (bsc#1265782).
- CVE-2026-39821: golang.org/x/net/idna: failure to reject ASCII-only Punycode-encoded labels allows for validation bypass and privilege escalation (bsc#1266625).
- CVE-2026-39984: github.com/sigstore/timestamp-authority/v2/pkg/verification: improper certificate validation can be used to bypass some authorization controls (bsc#1262346).
- CVE-2026-41567: arbitrary code execution with full daemon privileges when a user uploads a compressed archive into that container (bsc#1267827).
- Record
SUSE-SU-2026:22513-1- Updated
- 2026-11-02
OSVSUSE-SU-2026:24279-1 No score
Security update for docker
This update for docker fixes the following issues:
Security issues fixed:
- CVE-2026-33814: golang.org/x/net/http2: infinite loop in HTTP/2 transport when given bad SETTINGS_MAX_FRAME_SIZE (bsc#1265782).
- CVE-2026-39821: golang.org/x/net/idna: failure to reject ASCII-only Punycode-encoded labels allows for validation bypass and privilege escalation (bsc#1266625).
- CVE-2026-39984: github.com/sigstore/timestamp-authority/v2/pkg/verification: improper certificate validation can be used to bypass some authorization controls (bsc#1262346).
- CVE-2026-41567: arbitrary code execution with full daemon privileges when a user uploads a compressed archive into that container (bsc#1267827).
Non security issue fixed:
- SELinux CIL files are not shipped in Docker (bsc#1278193).
Changes for docker:
- Update to Docker 29.7.2. See upstream changelog online at https://docs.docker.com/engine/release-notes/29/#2972 fixes(bsc#1268280, bsc#1268359, bsc#1271209, bsc#1266176)
- Update to buildx 0.36.1. See upstream changelog online at https://github.com/docker/buildx/releases/tag/v0.36.1
- Record
SUSE-SU-2026:24279-1- Updated
- 2026-11-02
OSVSUSE-SU-2026:24318-1 No score
Security update for docker
This update for docker fixes the following issues:
Security issues fixed:
- CVE-2026-33814: golang.org/x/net/http2: infinite loop in HTTP/2 transport when given bad SETTINGS_MAX_FRAME_SIZE (bsc#1265782).
- CVE-2026-39821: golang.org/x/net/idna: failure to reject ASCII-only Punycode-encoded labels allows for validation bypass and privilege escalation (bsc#1266625).
- CVE-2026-39984: github.com/sigstore/timestamp-authority/v2/pkg/verification: improper certificate validation can be used to bypass some authorization controls (bsc#1262346).
- CVE-2026-41567: arbitrary code execution with full daemon privileges when a user uploads a compressed archive into that container (bsc#1267827).
Non security issue fixed:
- SELinux CIL files are not shipped in Docker (bsc#1278193).
Changes for docker:
- Update to Docker 29.7.2. See upstream changelog online at https://docs.docker.com/engine/release-notes/29/#2972
- Update to buildx 0.36.1. See upstream changelog online at https://github.com/docker/buildx/releases/tag/v0.36.1
- Record
SUSE-SU-2026:24318-1- Updated
- 2026-11-02
OSVSUSE-SU-2026:24410-1 No score
Security update for docker
This update for docker fixes the following issues:
Security issues fixed:
- CVE-2026-33814: golang.org/x/net/http2: infinite loop in HTTP/2 transport when given bad SETTINGS_MAX_FRAME_SIZE (bsc#1265782).
- CVE-2026-39821: golang.org/x/net/idna: failure to reject ASCII-only Punycode-encoded labels allows for validation bypass and privilege escalation (bsc#1266625).
- CVE-2026-39984: github.com/sigstore/timestamp-authority/v2/pkg/verification: improper certificate validation can be used to bypass some authorization controls (bsc#1262346).
- CVE-2026-41567: arbitrary code execution with full daemon privileges when a user uploads a compressed archive into that container (bsc#1267827).
Non security issue fixed:
- SELinux CIL files are not shipped in Docker (bsc#1278193).
Changes for docker:
- Update to Docker 29.7.2. See upstream changelog online at https://docs.docker.com/engine/release-notes/29/#2972 fixes(bsc#1268280, bsc#1268359, bsc#1271209, bsc#1266176)
- Update to buildx 0.36.1. See upstream changelog online at https://github.com/docker/buildx/releases/tag/v0.36.1
- Record
SUSE-SU-2026:24410-1- Updated
- 2026-11-02
OSVSUSE-SU-2026:2692-1 No score
Security update for docker
This update for docker fixes the following issues
- CVE-2026-33814: golang.org/x/net/http2: infinite loop in HTTP/2 transport when given bad SETTINGS_MAX_FRAME_SIZE (bsc#1265782).
- CVE-2026-39821: golang.org/x/net/idna: failure to reject ASCII-only Punycode-encoded labels allows for validation bypass and privilege escalation (bsc#1266625).
- CVE-2026-39984: github.com/sigstore/timestamp-authority/v2/pkg/verification: improper certificate validation can be used to bypass some authorization controls (bsc#1262346).
- CVE-2026-41567: arbitrary code execution with full daemon privileges when a user uploads a compressed archive into that container (bsc#1267827).
- Record
SUSE-SU-2026:2692-1- Updated
- 2026-11-02
OSVSUSE-SU-2026:4533-1 No score
Security update for docker-stable
This update for docker-stable fixes the following issues:
- CVE-2026-33186: google.golang.org/grpc: authorization bypass due to improper validation of the HTTP/2 :path pseudo- header (bsc#1260279).
- CVE-2026-33814: golang.org/x/net/http2: infinite loop in HTTP/2 transport when given bad SETTINGS_MAX_FRAME_SIZE (bsc#1265782).
- CVE-2026-39821: golang.org/x/net/idna: failure to reject ASCII-only Punycode-encoded labels allows for validation bypass and privilege escalation (bsc#1266625).
- CVE-2026-41567: arbitrary code execution with full daemon privileges when a user uploads a compressed archive into that container (bsc#1267827).
- Record
SUSE-SU-2026:4533-1- Updated
- 2026-11-02
OSVSUSE-SU-2026:4535-1 No score
Security update for docker-stable
This update for docker-stable fixes the following issues:
- CVE-2026-33186: google.golang.org/grpc: authorization bypass due to improper validation of the HTTP/2 :path pseudo- header (bsc#1260279).
- CVE-2026-33814: golang.org/x/net/http2: infinite loop in HTTP/2 transport when given bad SETTINGS_MAX_FRAME_SIZE (bsc#1265782).
- CVE-2026-39821: golang.org/x/net/idna: failure to reject ASCII-only Punycode-encoded labels allows for validation bypass and privilege escalation (bsc#1266625).
- CVE-2026-41567: arbitrary code execution with full daemon privileges when a user uploads a compressed archive into that container (bsc#1267827).
- Record
SUSE-SU-2026:4535-1- Updated
- 2026-11-02
Affected products
- docker engine
- docker docker/daemon
- moby docker engine
- moby moby/v2/daemon
- red hat exploit intelligence
- red hat multicluster engine for kubernetes
- red hat multicluster global hub 1.4.5
- red hat multicluster global hub 1.6.5
- red hat openshift developer tools and services 1.6.3
- red hat openshift lightspeed
- red hat advanced cluster management for kubernetes 2
- red hat ceph storage 5
Show 11 moreShow less
- red hat ceph storage 7
- red hat ceph storage 8
- red hat ceph storage 9
- red hat enterprise linux 10
- red hat enterprise linux 9
- red hat hardened images
- red hat multicluster global hub 1.5.3
- red hat openshift ai (rhoai)
- red hat openshift container platform 4
- red hat openshift data foundation 4.22
- red hat openshift distributed tracing 3
Affected packages
| Package | Affected | Fixed |
|---|---|---|
github.com/moby/moby/v2Go |
before 2.0.0-beta.14 | 2.0.0-beta.14 |
github.com/docker/dockerGo |
through 28.5.2 | None known |
github.com/moby/mobyGo |
through 28.5.2 | None known |
dockerAlpine:v3.23 |
before 29.5.1-r0 | 29.5.1-r0 |
dockerAlpine:v3.24 |
before 29.5.1-r0 | 29.5.1-r0 |
dockerAlpaquita:25 |
28.2.1-r0 up to 28.3.3-r17 | 28.3.3-r17 |
dockerAlpaquita:stream |
24.0.2-r0 up to 29.5.1-r0 | 29.5.1-r0 |
docker.ioDebian:12 |
All versions, plus listed versions 20.10.24+dfsg1-120.10.24+dfsg1-1+deb12u120.10.25+dfsg1-120.10.25+dfsg1-220.10.25+dfsg1-3 Show 42 moreShow less20.10.25+dfsg1-426.1.4+dfsg1-126.1.4+dfsg1-226.1.4+dfsg1-326.1.4+dfsg1-426.1.4+dfsg1-526.1.4+dfsg1-626.1.4+dfsg1-726.1.4+dfsg1-826.1.4+dfsg1-926.1.4+dfsg2-126.1.4+dfsg3-126.1.5+dfsg1-126.1.5+dfsg1-1026.1.5+dfsg1-226.1.5+dfsg1-326.1.5+dfsg1-426.1.5+dfsg1-526.1.5+dfsg1-626.1.5+dfsg1-726.1.5+dfsg1-826.1.5+dfsg1-927.5.1+dfsg1-127.5.1+dfsg1-227.5.1+dfsg2-127.5.1+dfsg3-127.5.1+dfsg3-227.5.1+dfsg3-327.5.1+dfsg3-427.5.1+dfsg3-527.5.1+dfsg3-627.5.1+dfsg4-127.5.1+dfsg4-228.5.2+dfsg1-128.5.2+dfsg2-128.5.2+dfsg3-128.5.2+dfsg3-228.5.2+dfsg4-128.5.2+dfsg4-228.5.2+dfsg4-328.5.2+dfsg4-428.5.2+dfsg4-5 |
None known |
docker.ioDebian:13 |
before 26.1.5+dfsg1-9+deb13u1, plus listed versions 26.1.5+dfsg1-9 |
26.1.5+dfsg1-9+deb13u1 |
docker.ioDebian:14 |
before 28.5.2+dfsg4-3, plus listed versions 26.1.5+dfsg1-1026.1.5+dfsg1-927.5.1+dfsg1-127.5.1+dfsg1-227.5.1+dfsg2-1 Show 14 moreShow less27.5.1+dfsg3-127.5.1+dfsg3-227.5.1+dfsg3-327.5.1+dfsg3-427.5.1+dfsg3-527.5.1+dfsg3-627.5.1+dfsg4-127.5.1+dfsg4-228.5.2+dfsg1-128.5.2+dfsg2-128.5.2+dfsg3-128.5.2+dfsg3-228.5.2+dfsg4-128.5.2+dfsg4-2 |
28.5.2+dfsg4-3 |
Show 60 moreShow less
| Package | Affected | Fixed |
|---|---|---|
github.com/docker/dockerGo |
All versions | None known |
github.com/moby/mobyGo |
All versions | None known |
github.com/docker/dockerRoot:Go |
before v28.5.2-aikido.9+incompatible | v28.5.2-aikido.9+incompatible |
rootio-github.com/docker/dockerRoot:Go |
before v28.5.2-root.io.9+incompatible | v28.5.2-root.io.9+incompatible |
dockerSUSE:Linux Micro 6.2 From an advisory covering 4 CVEs |
before 29.4.0_ce-160000.7.1 | 29.4.0_ce-160000.7.1 |
dockerSUSE:Linux Enterprise Server 16.0 From an advisory covering 4 CVEs |
before 29.4.0_ce-160000.7.1 | 29.4.0_ce-160000.7.1 |
dockerSUSE:Linux Enterprise Server for SAP applications 16.0 From an advisory covering 4 CVEs |
before 29.4.0_ce-160000.7.1 | 29.4.0_ce-160000.7.1 |
dockerSUSE:Linux Micro 6.1 From an advisory covering 4 CVEs |
before 29.4.0_ce-slfo.1.1_10.1 | 29.4.0_ce-slfo.1.1_10.1 |
dockerSUSE:Linux Micro 6.0 From an advisory covering 4 CVEs |
before 29.4.0_ce-11.1 | 29.4.0_ce-11.1 |
dockerSUSE:Linux Micro 6.1 From an advisory covering 5 CVEs |
before 29.7.2_ce-slfo.1.1_11.1 | 29.7.2_ce-slfo.1.1_11.1 |
dockerSUSE:Linux Micro 6.0 From an advisory covering 4 CVEs |
before 29.7.2_ce-159998.1.1 | 29.7.2_ce-159998.1.1 |
dockerSUSE:Linux Micro 6.2 From an advisory covering 5 CVEs |
before 29.7.2_ce-160000.8.1 | 29.7.2_ce-160000.8.1 |
dockerSUSE:Linux Enterprise Micro 5.3 From an advisory covering 4 CVEs |
before 29.4.0_ce-150000.253.1 | 29.4.0_ce-150000.253.1 |
dockerSUSE:Linux Enterprise Micro 5.4 From an advisory covering 4 CVEs |
before 29.4.0_ce-150000.253.1 | 29.4.0_ce-150000.253.1 |
dockerSUSE:Linux Enterprise Micro 5.5 From an advisory covering 4 CVEs |
before 29.4.0_ce-150000.253.1 | 29.4.0_ce-150000.253.1 |
dockerSUSE:Linux Enterprise Module for Basesystem 15 SP7 From an advisory covering 4 CVEs |
before 29.4.0_ce-150000.253.1 | 29.4.0_ce-150000.253.1 |
dockerSUSE:Linux Enterprise Module for Containers 15 SP7 From an advisory covering 4 CVEs |
before 29.4.0_ce-150000.253.1 | 29.4.0_ce-150000.253.1 |
dockerSUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS From an advisory covering 4 CVEs |
before 29.4.0_ce-150000.253.1 | 29.4.0_ce-150000.253.1 |
dockerSUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS From an advisory covering 4 CVEs |
before 29.4.0_ce-150000.253.1 | 29.4.0_ce-150000.253.1 |
dockerSUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS From an advisory covering 4 CVEs |
before 29.4.0_ce-150000.253.1 | 29.4.0_ce-150000.253.1 |
dockerSUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS From an advisory covering 4 CVEs |
before 29.4.0_ce-150000.253.1 | 29.4.0_ce-150000.253.1 |
dockerSUSE:Linux Enterprise Server 15 SP4-LTSS From an advisory covering 4 CVEs |
before 29.4.0_ce-150000.253.1 | 29.4.0_ce-150000.253.1 |
dockerSUSE:Linux Enterprise Server 15 SP5-LTSS From an advisory covering 4 CVEs |
before 29.4.0_ce-150000.253.1 | 29.4.0_ce-150000.253.1 |
dockerSUSE:Linux Enterprise Server 15 SP6-LTSS From an advisory covering 4 CVEs |
before 29.4.0_ce-150000.253.1 | 29.4.0_ce-150000.253.1 |
dockerSUSE:Linux Enterprise Server for SAP Applications 15 SP4 From an advisory covering 4 CVEs |
before 29.4.0_ce-150000.253.1 | 29.4.0_ce-150000.253.1 |
dockerSUSE:Linux Enterprise Server for SAP Applications 15 SP5 From an advisory covering 4 CVEs |
before 29.4.0_ce-150000.253.1 | 29.4.0_ce-150000.253.1 |
dockerSUSE:Linux Enterprise Server for SAP Applications 15 SP6 From an advisory covering 4 CVEs |
before 29.4.0_ce-150000.253.1 | 29.4.0_ce-150000.253.1 |
docker-stableSUSE:Linux Enterprise Server 12 SP5-LTSS From an advisory covering 4 CVEs |
before 24.0.9_ce-1.40.1 | 24.0.9_ce-1.40.1 |
docker-stableSUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 From an advisory covering 4 CVEs |
before 24.0.9_ce-1.40.1 | 24.0.9_ce-1.40.1 |
docker-stableSUSE:Linux Enterprise Module for Containers 15 SP7 From an advisory covering 4 CVEs |
before 24.0.9_ce-150000.1.48.1 | 24.0.9_ce-150000.1.48.1 |
docker-stableSUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS From an advisory covering 4 CVEs |
before 24.0.9_ce-150000.1.48.1 | 24.0.9_ce-150000.1.48.1 |
docker-stableSUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS From an advisory covering 4 CVEs |
before 24.0.9_ce-150000.1.48.1 | 24.0.9_ce-150000.1.48.1 |
docker-stableSUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS From an advisory covering 4 CVEs |
before 24.0.9_ce-150000.1.48.1 | 24.0.9_ce-150000.1.48.1 |
docker-stableSUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS From an advisory covering 4 CVEs |
before 24.0.9_ce-150000.1.48.1 | 24.0.9_ce-150000.1.48.1 |
docker-stableSUSE:Linux Enterprise Server 15 SP4-LTSS From an advisory covering 4 CVEs |
before 24.0.9_ce-150000.1.48.1 | 24.0.9_ce-150000.1.48.1 |
docker-stableSUSE:Linux Enterprise Server 15 SP5-LTSS From an advisory covering 4 CVEs |
before 24.0.9_ce-150000.1.48.1 | 24.0.9_ce-150000.1.48.1 |
docker-stableSUSE:Linux Enterprise Server 15 SP6-LTSS From an advisory covering 4 CVEs |
before 24.0.9_ce-150000.1.48.1 | 24.0.9_ce-150000.1.48.1 |
docker-stableSUSE:Linux Enterprise Server for SAP Applications 15 SP4 From an advisory covering 4 CVEs |
before 24.0.9_ce-150000.1.48.1 | 24.0.9_ce-150000.1.48.1 |
docker-stableSUSE:Linux Enterprise Server for SAP Applications 15 SP5 From an advisory covering 4 CVEs |
before 24.0.9_ce-150000.1.48.1 | 24.0.9_ce-150000.1.48.1 |
docker-stableSUSE:Linux Enterprise Server for SAP Applications 15 SP6 From an advisory covering 4 CVEs |
before 24.0.9_ce-150000.1.48.1 | 24.0.9_ce-150000.1.48.1 |
docker.ioUbuntu:Pro:16.04:LTS |
All versions, plus listed versions 1.6.2~dfsg1-1ubuntu41.10.2-0ubuntu31.10.2-0ubuntu41.10.3-0ubuntu11.10.3-0ubuntu4 Show 19 moreShow less1.10.3-0ubuntu51.10.3-0ubuntu61.11.2-0ubuntu5~16.041.12.1-0ubuntu13~16.04.11.12.3-0ubuntu4~16.04.21.12.6-0ubuntu1~16.04.11.13.1-0ubuntu1~16.04.217.03.2-0ubuntu2~16.04.118.06.1-0ubuntu1~16.04.218.06.1-0ubuntu1.2~16.04.118.09.2-0ubuntu1~16.04.118.09.5-0ubuntu1~16.04.218.09.7-0ubuntu1~16.04.118.09.7-0ubuntu1~16.04.418.09.7-0ubuntu1~16.04.518.09.7-0ubuntu1~16.04.618.09.7-0ubuntu1~16.04.718.09.7-0ubuntu1~16.04.9+esm118.09.7-0ubuntu1~16.04.9+esm2 |
None known |
docker.ioUbuntu:Pro:18.04:LTS |
All versions, plus listed versions 1.13.1-0ubuntu617.03.2-0ubuntu117.03.2-0ubuntu317.03.2-0ubuntu517.12.1-0ubuntu1 Show 22 moreShow less18.06.1-0ubuntu1~18.04.118.06.1-0ubuntu1.2~18.04.118.09.2-0ubuntu1~18.04.118.09.5-0ubuntu1~18.04.218.09.7-0ubuntu1~18.04.118.09.7-0ubuntu1~18.04.318.09.7-0ubuntu1~18.04.419.03.6-0ubuntu1~18.04.119.03.6-0ubuntu1~18.04.219.03.6-0ubuntu1~18.04.320.10.2-0ubuntu1~18.04.220.10.2-0ubuntu1~18.04.320.10.7-0ubuntu1~18.04.120.10.7-0ubuntu1~18.04.220.10.7-0ubuntu5~18.04.220.10.7-0ubuntu5~18.04.320.10.12-0ubuntu2~18.04.120.10.21-0ubuntu1~18.04.220.10.21-0ubuntu1~18.04.320.10.21-0ubuntu1~18.04.3+esm120.10.21-0ubuntu1~18.04.3+esm220.10.21-0ubuntu1~18.04.3+esm3 |
None known |
docker.ioUbuntu:Pro:20.04:LTS |
All versions, plus listed versions 19.03.2-0ubuntu119.03.6-0ubuntu119.03.8-0ubuntu119.03.8-0ubuntu1.20.0419.03.8-0ubuntu1.20.04.1 Show 15 moreShow less19.03.8-0ubuntu1.20.04.220.10.2-0ubuntu1~20.04.220.10.2-0ubuntu1~20.04.320.10.7-0ubuntu1~20.04.120.10.7-0ubuntu1~20.04.220.10.7-0ubuntu5~20.04.120.10.7-0ubuntu5~20.04.220.10.12-0ubuntu2~20.04.120.10.21-0ubuntu1~20.04.120.10.21-0ubuntu1~20.04.220.10.21-0ubuntu1~20.04.420.10.21-0ubuntu1~20.04.520.10.21-0ubuntu1~20.04.620.10.21-0ubuntu1~20.04.6+esm120.10.21-0ubuntu1~20.04.6+esm2 |
None known |
docker.io-appUbuntu:Pro:20.04:LTS |
All versions, plus listed versions 20.10.25-0ubuntu1~20.04.120.10.25-0ubuntu1~20.04.224.0.5-0ubuntu1~20.04.124.0.7-0ubuntu2~20.04.126.1.3-0ubuntu1~20.04.126.1.3-0ubuntu1~20.04.1+esm126.1.3-0ubuntu1~20.04.1+esm2 |
None known |
docker.ioUbuntu:Pro:22.04:LTS |
All versions, plus listed versions 20.10.7-0ubuntu520.10.7-0ubuntu720.10.12-0ubuntu120.10.12-0ubuntu220.10.12-0ubuntu3 Show 11 moreShow less20.10.12-0ubuntu3+gke1.24.120.10.12-0ubuntu420.10.21-0ubuntu1~22.04.220.10.21-0ubuntu1~22.04.320.10.21-0ubuntu1~22.04.520.10.21-0ubuntu1~22.04.620.10.21-0ubuntu1~22.04.720.10.21-0ubuntu1~22.04.7+esm120.10.21-0ubuntu1~22.04.7+esm220.10.21-0ubuntu1~22.04.820.10.21-0ubuntu1~22.04.8+esm1 |
None known |
docker.io-appUbuntu:Pro:22.04:LTS |
All versions, plus listed versions 20.10.25-0ubuntu1~22.04.120.10.25-0ubuntu1~22.04.224.0.5-0ubuntu1~22.04.124.0.7-0ubuntu2~22.04.126.1.3-0ubuntu1~22.04.1 Show 6 moreShow less26.1.3-0ubuntu1~22.04.1+esm127.5.1-0ubuntu3~22.04.127.5.1-0ubuntu3~22.04.228.2.2-0ubuntu1~22.04.129.1.3-0ubuntu3~22.04.129.1.3-0ubuntu3~22.04.2 |
None known |
docker.ioUbuntu:Pro:24.04:LTS |
All versions, plus listed versions 20.10.24+dfsg1-1ubuntu220.10.25+dfsg1-2ubuntu120.10.25+dfsg1-2ubuntu1+esm120.10.25+dfsg1-2ubuntu1+esm220.10.25+dfsg1-2ubuntu1.24.04.120.10.25+dfsg1-2ubuntu1.24.04.1+esm1 |
None known |
docker.io-appUbuntu:Pro:24.04:LTS |
All versions, plus listed versions 24.0.5-0ubuntu124.0.7-0ubuntu124.0.7-0ubuntu224.0.7-0ubuntu324.0.7-0ubuntu4 Show 8 moreShow less24.0.7-0ubuntu4.126.1.3-0ubuntu1~24.04.126.1.3-0ubuntu1~24.04.1+esm127.5.1-0ubuntu3~24.04.127.5.1-0ubuntu3~24.04.228.2.2-0ubuntu1~24.04.129.1.3-0ubuntu3~24.04.129.1.3-0ubuntu3~24.04.2 |
None known |
docker.ioUbuntu:25.10 |
All versions, plus listed versions 26.1.5+dfsg1-9ubuntu1 |
None known |
docker.io-appUbuntu:25.10 |
All versions, plus listed versions 27.5.1-0ubuntu327.5.1-0ubuntu428.2.2-0ubuntu129.1.3-0ubuntu3~25.10.1 |
None known |
docker.ioUbuntu:26.10 |
All versions, plus listed versions 27.5.1+dfsg4-2ubuntu128.5.2+dfsg4-5ubuntu1 |
None known |
docker.io-appUbuntu:26.10 |
All versions, plus listed versions 29.1.3-0ubuntu429.1.3-0ubuntu529.1.3-0ubuntu629.7.2-0ubuntu1 |
None known |
docker.ioUbuntu:26.04:LTS |
All versions, plus listed versions 26.1.5+dfsg1-9ubuntu127.5.1+dfsg4-1ubuntu127.5.1+dfsg4-2ubuntu1 |
None known |
docker.io-appUbuntu:26.04:LTS |
All versions, plus listed versions 28.2.2-0ubuntu129.1.2-0ubuntu129.1.3-0ubuntu129.1.3-0ubuntu229.1.3-0ubuntu329.1.3-0ubuntu429.1.3-0ubuntu4.1 |
None known |
docker-stableopenSUSE:Tumbleweed From an advisory covering 8 CVEs |
before 24.0.9_ce-18.1 | 24.0.9_ce-18.1 |
dockeropenSUSE:Tumbleweed From an advisory covering 4 CVEs |
before 29.4.0_ce-40.1 | 29.4.0_ce-40.1 |
dockeropenSUSE:Leap 16.0 From an advisory covering 4 CVEs |
before 29.4.0_ce-160000.7.1 | 29.4.0_ce-160000.7.1 |
docker-stableopenSUSE:Leap 16.0 From an advisory covering 6 CVEs |
before 24.0.9_ce-160000.6.1 | 24.0.9_ce-160000.6.1 |
govulncheck-vulndbopenSUSE:Leap 16.0 From an advisory covering 1734 CVEs |
before 0.0.20260723T184607-160000.1.1 | 0.0.20260723T184607-160000.1.1 |
dockeropenSUSE:Leap 16.0 From an advisory covering 5 CVEs |
before 29.7.2_ce-160000.8.1 | 29.7.2_ce-160000.8.1 |
Public exploits
Links only. Every CVE stores no exploit code.
| Source | Link | Date |
|---|---|---|
| PoC in GitHub | berdav/CVE-2026-41567 | 2026-08-21 |
History
| Recorded | Changed | Sources |
|---|---|---|
| affected, facts | ||
| affected | OSV | |
| affected, aliases, references | OSV | |
| first indexed | CVE List, EUVD, GitHub Advisories, NVD, OSV, PoC in GitHub |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2026-41567 is a high vulnerability (CVSS 7.2) in Docker Engine, published May 18, 2026. Public exploit code exists. EPSS puts the chance of exploitation in the next 30 days at 0.15%, the 4th percentile. Fixed in github.com/moby/moby/v2 2.0.0-beta.14.
References
github.com/moby/moby/security/advisories/GHSA-x86f-5xw2-fm2r
access.redhat.com/security/cve/CVE-2026-41567
bugzilla.redhat.com/show_bug.cgi?id=2485356
security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-41567.json
access.redhat.com/errata/RHSA-2026:41030
access.redhat.com/errata/RHSA-2026:44622
Show 194 moreShow less
access.redhat.com/errata/RHSA-2026:51057
access.redhat.com/errata/RHSA-2026:37387
access.redhat.com/errata/RHSA-2026:42852
nvd.nist.gov/vuln/detail/CVE-2026-41567
github.com/advisories/GHSA-x86f-5xw2-fm2r
security.alpinelinux.org/vuln/CVE-2026-41567
docs.bell-sw.com/security/cves/CVE-2026-41567
github.com/CVEProject/cvelistV5/tree/main/cves/2026/41xxx/CVE-2026-41567.json
security-tracker.debian.org/tracker/CVE-2026-41567
github.com/moby/moby
suse.com/support/update/announcement/2026/suse-su-202622285-1
bugzilla.suse.com/1262346
bugzilla.suse.com/1265782
bugzilla.suse.com/1266625
bugzilla.suse.com/1267827
suse.com/security/cve/CVE-2026-33814
suse.com/security/cve/CVE-2026-39821
suse.com/security/cve/CVE-2026-39984
suse.com/security/cve/CVE-2026-41567
suse.com/support/update/announcement/2026/suse-su-202622367-1
suse.com/support/update/announcement/2026/suse-su-202622456-1
suse.com/support/update/announcement/2026/suse-su-202622513-1
suse.com/support/update/announcement/2026/suse-su-202624279-1
bugzilla.suse.com/1073877
bugzilla.suse.com/1099277
bugzilla.suse.com/1266176
bugzilla.suse.com/1268280
bugzilla.suse.com/1268359
bugzilla.suse.com/1271209
bugzilla.suse.com/1278193
suse.com/security/cve/CVE-2026-31431
suse.com/support/update/announcement/2026/suse-su-202624318-1
suse.com/support/update/announcement/2026/suse-su-202624410-1
suse.com/support/update/announcement/2026/suse-su-20262692-1
suse.com/support/update/announcement/2026/suse-su-20264533-1
bugzilla.suse.com/1260279
suse.com/security/cve/CVE-2026-33186
suse.com/support/update/announcement/2026/suse-su-20264535-1
ubuntu.com/security/CVE-2026-41567
cve.org/CVERecord?id=CVE-2026-41567
suse.com/security/cve/CVE-2026-33747
suse.com/security/cve/CVE-2026-33748
suse.com/security/cve/CVE-2026-33997
suse.com/security/cve/CVE-2026-34040
bugzilla.suse.com/1265907
bugzilla.suse.com/1265929
suse.com/security/cve/CVE-2016-11063
suse.com/security/cve/CVE-2016-11066
suse.com/security/cve/CVE-2016-11067
suse.com/security/cve/CVE-2016-11068
suse.com/security/cve/CVE-2016-11069
suse.com/security/cve/CVE-2016-11070
suse.com/security/cve/CVE-2016-11071
suse.com/security/cve/CVE-2016-11072
suse.com/security/cve/CVE-2016-11073
suse.com/security/cve/CVE-2016-11074
suse.com/security/cve/CVE-2016-11075
suse.com/security/cve/CVE-2016-11076
suse.com/security/cve/CVE-2016-11077
suse.com/security/cve/CVE-2016-11078
suse.com/security/cve/CVE-2016-11079
suse.com/security/cve/CVE-2016-11080
suse.com/security/cve/CVE-2016-11081
suse.com/security/cve/CVE-2016-11082
suse.com/security/cve/CVE-2016-11083
suse.com/security/cve/CVE-2016-11084
suse.com/security/cve/CVE-2017-18870
suse.com/security/cve/CVE-2017-18871
suse.com/security/cve/CVE-2017-18872
suse.com/security/cve/CVE-2017-18873
suse.com/security/cve/CVE-2017-18874
suse.com/security/cve/CVE-2017-18875
suse.com/security/cve/CVE-2017-18876
suse.com/security/cve/CVE-2017-18877
suse.com/security/cve/CVE-2017-18878
suse.com/security/cve/CVE-2017-18879
suse.com/security/cve/CVE-2017-18883
suse.com/security/cve/CVE-2017-18884
suse.com/security/cve/CVE-2017-18885
suse.com/security/cve/CVE-2017-18886
suse.com/security/cve/CVE-2017-18887
suse.com/security/cve/CVE-2017-18888
suse.com/security/cve/CVE-2017-18889
suse.com/security/cve/CVE-2017-18890
suse.com/security/cve/CVE-2017-18891
suse.com/security/cve/CVE-2017-18892
suse.com/security/cve/CVE-2017-18893
suse.com/security/cve/CVE-2017-18894
suse.com/security/cve/CVE-2017-18895
suse.com/security/cve/CVE-2017-18896
suse.com/security/cve/CVE-2017-18897
suse.com/security/cve/CVE-2017-18898
suse.com/security/cve/CVE-2017-18900
suse.com/security/cve/CVE-2017-18901
suse.com/security/cve/CVE-2017-18902
suse.com/security/cve/CVE-2017-18903
suse.com/security/cve/CVE-2017-18904
suse.com/security/cve/CVE-2017-18905
suse.com/security/cve/CVE-2017-18906
suse.com/security/cve/CVE-2017-18907
suse.com/security/cve/CVE-2017-18908
suse.com/security/cve/CVE-2017-18909
suse.com/security/cve/CVE-2017-18911
suse.com/security/cve/CVE-2017-18912
suse.com/security/cve/CVE-2017-18915
suse.com/security/cve/CVE-2017-18916
suse.com/security/cve/CVE-2017-18917
suse.com/security/cve/CVE-2017-18918
suse.com/security/cve/CVE-2018-21258
suse.com/security/cve/CVE-2019-8400
suse.com/security/cve/CVE-2021-25320
suse.com/security/cve/CVE-2022-45786
suse.com/security/cve/CVE-2023-26154
suse.com/security/cve/CVE-2023-32199
suse.com/security/cve/CVE-2023-34620
suse.com/security/cve/CVE-2023-43630
suse.com/security/cve/CVE-2023-43631
suse.com/security/cve/CVE-2023-43632
suse.com/security/cve/CVE-2023-43633
suse.com/security/cve/CVE-2023-43634
suse.com/security/cve/CVE-2023-43635
suse.com/security/cve/CVE-2023-43636
suse.com/security/cve/CVE-2023-43637
suse.com/security/cve/CVE-2023-47108
suse.com/security/cve/CVE-2024-12886
suse.com/security/cve/CVE-2024-21635
suse.com/security/cve/CVE-2024-25621
suse.com/security/cve/CVE-2024-41260
suse.com/security/cve/CVE-2024-41265
suse.com/security/cve/CVE-2024-44905
suse.com/security/cve/CVE-2024-52284
suse.com/security/cve/CVE-2024-53412
suse.com/security/cve/CVE-2024-58259
suse.com/security/cve/CVE-2024-58260
suse.com/security/cve/CVE-2024-58267
suse.com/security/cve/CVE-2024-58269
suse.com/security/cve/CVE-2024-6717
suse.com/security/cve/CVE-2025-0426
suse.com/security/cve/CVE-2025-10543
suse.com/security/cve/CVE-2025-10545
suse.com/security/cve/CVE-2025-10630
suse.com/security/cve/CVE-2025-10678
suse.com/security/cve/CVE-2025-10954
suse.com/security/cve/CVE-2025-11374
suse.com/security/cve/CVE-2025-11375
suse.com/security/cve/CVE-2025-11393
suse.com/security/cve/CVE-2025-11579
suse.com/security/cve/CVE-2025-11621
suse.com/security/cve/CVE-2025-11776
suse.com/security/cve/CVE-2025-11777
suse.com/security/cve/CVE-2025-11794
suse.com/security/cve/CVE-2025-12044
suse.com/security/cve/CVE-2025-12419
suse.com/security/cve/CVE-2025-12421
suse.com/security/cve/CVE-2025-12559
suse.com/security/cve/CVE-2025-12689
suse.com/security/cve/CVE-2025-12756
suse.com/security/cve/CVE-2025-13281
suse.com/security/cve/CVE-2025-13324
suse.com/security/cve/CVE-2025-13352
suse.com/security/cve/CVE-2025-13353
suse.com/security/cve/CVE-2025-13357
suse.com/security/cve/CVE-2025-13425
suse.com/security/cve/CVE-2025-13523
suse.com/security/cve/CVE-2025-13767
suse.com/security/cve/CVE-2025-13821
suse.com/security/cve/CVE-2025-13870
suse.com/security/cve/CVE-2025-13888
suse.com/security/cve/CVE-2025-14273
suse.com/security/cve/CVE-2025-14350
suse.com/security/cve/CVE-2025-14435
suse.com/security/cve/CVE-2025-14443
suse.com/security/cve/CVE-2025-14525
suse.com/security/cve/CVE-2025-14573
suse.com/security/cve/CVE-2025-14764
suse.com/security/cve/CVE-2025-14822
suse.com/security/cve/CVE-2025-14986
suse.com/security/cve/CVE-2025-14987
suse.com/security/cve/CVE-2025-15107
suse.com/security/cve/CVE-2025-15558
suse.com/security/cve/CVE-2025-21613
suse.com/security/cve/CVE-2025-22870
suse.com/security/cve/CVE-2025-22873
suse.com/security/cve/CVE-2025-23266
suse.com/security/cve/CVE-2025-23267
suse.com/security/cve/CVE-2025-26625
suse.com/security/cve/CVE-2025-27093
suse.com/security/cve/CVE-2025-2786
suse.com/security/cve/CVE-2025-2842
suse.com/security/cve/CVE-2025-2843
suse.com/security/cve/CVE-2025-31133
suse.com/security/cve/CVE-2025-34410
suse.com/security/cve/CVE-2025-34429
suse.com/security/cve/CVE-2025-34430
Left out here: 1,577 references and the rest of 1 source description. The JSON record has them.