Repository navigation
chore(deps): update module github.com/containerd/containerd to v2 [security] - #198
Open
alaudaa-renovate[bot] wants to merge 1 commit into
Open
alaudaa-renovate[bot] wants to merge 1 commit into
alaudaa-renovate[bot] wants to merge 1 commit into
Conversation
alaudaa-renovate
Bot
force-pushed
the
renovate/go-github.com-containerd-containerd-vulnerability
branch
from
June 18, 2026 00:08
d568424 to
5bbfe1a
Compare
alaudaa-renovate
Bot
force-pushed
the
renovate/go-github.com-containerd-containerd-vulnerability
branch
from
June 22, 2026 17:44
5bbfe1a to
fab7db2
Compare
alaudaa-renovate
Bot
force-pushed
the
renovate/go-github.com-containerd-containerd-vulnerability
branch
from
July 18, 2026 14:44
fab7db2 to
2d66702
Compare
alaudaa-renovate
Bot
force-pushed
the
renovate/go-github.com-containerd-containerd-vulnerability
branch
from
September 10, 2026 10:18
2d66702 to
96bebe7
Compare
Contributor
Author
ℹ Artifact update noticeFile name: artifact-scanner/go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
alaudaa-renovate
Bot
force-pushed
the
renovate/go-github.com-containerd-containerd-vulnerability
branch
from
September 14, 2026 13:35
96bebe7 to
7203df0
Compare
alaudaa-renovate
Bot
force-pushed
the
renovate/go-github.com-containerd-containerd-vulnerability
branch
from
September 26, 2026 12:57
7203df0 to
cb58470
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.7.29->v2.0.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
GitHub Vulnerability Alerts
CVE-2026-46680
Impact
A bug was found in containerd where containers launched with a numeric
Userdirective that cannot be parsed as a 32-bit integer are incorrectly treated as a username. If a crafted image provides an/etc/passwdfile mapping this large numeric string to root, the container ultimately runs as root (UID 0). This allows the KubernetesrunAsNonRootrestriction to be bypassed, causing unexpected behavior for environments that require containers to run as a non-root user.Patches
This bug has been fixed in the following containerd versions:
Note: The containerd 2.1 release has reached its end of life and a fixed version is not provided.
Users should update to these versions to resolve the issue.
Workarounds
Ensure that only trusted images are used and that only trusted users have permissions to import images. Alternatively, enforcing a specific numeric
runAsUserin the Kubernetes PodsecurityContextoverrides theUSERdirective in the image and prevents the bypass. Newer versions of Kubernetes, starting with 1.34, also appear to enforcerunAsNonRootproperly regardless of this bug.Credits
The containerd project would like to thank Lei Wang (@ssst0n3) for responsibly disclosing this issue in accordance with the containerd security policy.
Resources
For more information
If there are any questions or comments about this advisory:
To report a security issue in containerd:
CVE-2026-47262
Impact
A vulnerability in containerd allows a maliciously crafted image to cause a Denial of Service (DoS) condition. When creating a container from this image, memory exhaustion occurs, leading to an Out Of Memory (OOM) kill of the containerd process. This renders the container runtime API unavailable and can disrupt clients such as the Docker Engine or Kubernetes control-plane components.
Patches
This bug has been fixed in the following containerd versions:
Users should update to these versions to resolve the issue.
Workarounds
Ensure that only trusted images are used and that only trusted users have permissions to import images or schedule pods.
Credits
The containerd project would like to thank Jakub Ciolek (@jake-ciolek) at AlphaSense and Kyle Elliott @ Trail of Bits who independently discovered and responsibly disclosed this issue in accordance with the containerd security policy.
For more information
If you have any questions or comments about this advisory:
To report a security issue in containerd:
CVE-2026-53488
Impact
A bug was found in containerd where the CRI plugin propagates labels from an image config (
LABELinstruction in Dockerfile) to a container without validation. This may result in executing an arbitrary command on the host, via a plugin that consumes container labels for some operations.Patches
This bug has been fixed in the following containerd versions:
Users should update to these versions to resolve the issue.
Workarounds
Ensure that only trusted images are used.
Credits
The containerd project would like to thank Anthropic Research, in collaboration with Claude, the GKE Security Team using Gemini, and Robert Prast (@robertprast) for independently discovering and responsibly disclosing this issue in accordance with the containerd security policy.
For more information
If you have any questions or comments about this advisory:
To report a security issue in containerd:
CVE-2026-53495
Impact
A bug in containerd's CRI ExecSync implementation allows exec probes and lifecycle hooks with background child processes to keep containerd's stdio-drain goroutines indefinitely blocked. Because the I/O drain phase lacks a default timeout or context cancellation handling, repeated ExecSync invocations (like probes) that include long-lived background processes against a container can cause containerd to leak goroutines and host memory. Over time, this resource exhaustion can cause the containerd daemon to be terminated by the OOM killer, rendering containerd unavailable until it is restarted. This issue affects containerd on Linux systems running with the CRI plugin enabled. Users not using containerd's CRI implementation or not running containers on Linux are not affected.
Patches
This bug has been fixed in containerd 2.3.5, 2.2.8, 2.0.12, and 1.7.35. Users should update to these versions to resolve the issue.
Workarounds
Ensure exec probes and lifecycle hooks do not launch long-lived background child processes.
Credits
The containerd project would like to thank XlabAI Team of Tencent Xuanwu Lab (xlabai@tencent.com), including Guannan Wang, Zhanpeng Liu, Jiashuo Liang, and Guancheng Li, and @IamwhatIamSY who independently discovered and responsibly disclosed this issue in accordance with the containerd security policy.
For more information
If there are any questions or comments about this advisory:
To report a security issue in containerd:
CVE-2026-53493
Impact
A vulnerability exists in containerd's image pull handlers where a crafted OCI image index containing deeply nested or heavily fanned-out descriptor graphs can cause unbounded CPU and memory consumption. During the
PullImageoperation, the recursive traversal and processing of child descriptors lack sufficient depth and breadth limits, and fail to adequately deduplicate identical descriptors. This unbounded traversal leads to excessive resource allocation.Consequently, pulling a malicious image reference can result in prolonged stalls during container creation and significant resource pressure on the host system. This issue occurs entirely during the image pull phase, prior to any container execution.
Patches
This bug has been fixed in containerd 2.4.1, 2.3.6, 2.2.9, 2.0.13, and 1.7.36. Users should update to these versions to resolve the issue.
Workarounds
There are no known workarounds for this issue. Users are advised to only pull trusted images from known registries until the patch can be applied.
Credits
The containerd project would like to thank Jakub Ciolek at ElevenLabs and @jlgore who independently discovered and responsibly disclosed this issue in accordance with the containerd security policy.
For more information
If you have any questions or comments about this advisory:
To report a security issue in containerd:
containerd user ID handling bypass allows runAsNonRoot evasion in github.com/containerd/containerd
CVE-2026-46680 / GHSA-fqw6-gf59-qr4w / GO-2026-5378
More information
Details
containerd user ID handling bypass allows runAsNonRoot evasion in github.com/containerd/containerd
Severity
Unknown
References
This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).
containerd user ID handling bypass allows runAsNonRoot evasion
CVE-2026-46680 / GHSA-fqw6-gf59-qr4w / GO-2026-5378
More information
Details
Impact
A bug was found in containerd where containers launched with a numeric
Userdirective that cannot be parsed as a 32-bit integer are incorrectly treated as a username. If a crafted image provides an/etc/passwdfile mapping this large numeric string to root, the container ultimately runs as root (UID 0). This allows the KubernetesrunAsNonRootrestriction to be bypassed, causing unexpected behavior for environments that require containers to run as a non-root user.Patches
This bug has been fixed in the following containerd versions:
Note: The containerd 2.1 release has reached its end of life and a fixed version is not provided.
Users should update to these versions to resolve the issue.
Workarounds
Ensure that only trusted images are used and that only trusted users have permissions to import images. Alternatively, enforcing a specific numeric
runAsUserin the Kubernetes PodsecurityContextoverrides theUSERdirective in the image and prevents the bypass. Newer versions of Kubernetes, starting with 1.34, also appear to enforcerunAsNonRootproperly regardless of this bug.Credits
The containerd project would like to thank Lei Wang (@ssst0n3) for responsibly disclosing this issue in accordance with the containerd security policy.
Resources
For more information
If there are any questions or comments about this advisory:
To report a security issue in containerd:
Severity
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
containerd image-triggered runtime DoS via unbounded group parsing
CVE-2026-47262 / GHSA-jpcc-p29g-p8mq / GO-2026-5475
More information
Details
Impact
A vulnerability in containerd allows a maliciously crafted image to cause a Denial of Service (DoS) condition. When creating a container from this image, memory exhaustion occurs, leading to an Out Of Memory (OOM) kill of the containerd process. This renders the container runtime API unavailable and can disrupt clients such as the Docker Engine or Kubernetes control-plane components.
Patches
This bug has been fixed in the following containerd versions:
Users should update to these versions to resolve the issue.
Workarounds
Ensure that only trusted images are used and that only trusted users have permissions to import images or schedule pods.
Credits
The containerd project would like to thank Jakub Ciolek (@jake-ciolek) at AlphaSense and Kyle Elliott @ Trail of Bits who independently discovered and responsibly disclosed this issue in accordance with the containerd security policy.
For more information
If you have any questions or comments about this advisory:
To report a security issue in containerd:
Severity
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
containerd CRI — image-config
LABELflows to restart-monitorbinary://logger: host-root command execution from an image pullCVE-2026-53488 / GHSA-xhf5-7wjv-pqxp / GO-2026-5758
More information
Details
Impact
A bug was found in containerd where the CRI plugin propagates labels from an image config (
LABELinstruction in Dockerfile) to a container without validation. This may result in executing an arbitrary command on the host, via a plugin that consumes container labels for some operations.Patches
This bug has been fixed in the following containerd versions:
Users should update to these versions to resolve the issue.
Workarounds
Ensure that only trusted images are used.
Credits
The containerd project would like to thank Anthropic Research, in collaboration with Claude, the GKE Security Team using Gemini, and Robert Prast (@robertprast) for independently discovering and responsibly disclosing this issue in accordance with the containerd security policy.
For more information
If you have any questions or comments about this advisory:
To report a security issue in containerd:
Severity
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
containerd image-triggered runtime DoS via unbounded group parsing in github.com/containerd/containerd
CVE-2026-47262 / GHSA-jpcc-p29g-p8mq / GO-2026-5475
More information
Details
containerd image-triggered runtime DoS via unbounded group parsing in github.com/containerd/containerd
Severity
Unknown
References
This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).
containerd CRI — image-config
LABELflows to restart-monitorbinary://logger: host-root command execution from an image pull in github.com/containerd/containerdCVE-2026-53488 / GHSA-xhf5-7wjv-pqxp / GO-2026-5758
More information
Details
containerd CRI — image-config
LABELflows to restart-monitorbinary://logger: host-root command execution from an image pull in github.com/containerd/containerdSeverity
Unknown
References
This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).
Release Notes
containerd/containerd (github.com/containerd/containerd)
v2.0.0: containerd 2.0.0Compare Source
Welcome to the v2.0.0 release of containerd!
The first major release of containerd 2.x focuses on the continued stability of
containerd's core feature set with an easy upgrade from containerd 1.x. This
release includes the stabilization of new features added in the last 1.x release
as well as the removal of features which were deprecated in 1.x. The goal is to
support the vast community of containerd users well into the future along with
their ever increasing deployment footprints and variety of use cases.
See containerd 2.0 documentation for details on what is new and has changed in this release.
Highlights
LimitNOFILEfromcontainerd.service(#8924)aufssnapshotter (#8263)Build and Release Toolchain
cri-containerd-*.tar.gzrelease bundles (#9096)Container Runtime Interface (CRI)
Go client
Image Distribution
Runtime
io.containerd.runtime.v1.linuxandio.containerd.runc.v1(#8262)Security Advisories
Breaking
disable_cgroupfrom CRI config (#10594)LimitNOFILEfromcontainerd.service(#8924)io.containerd.runtime.v1.linuxandio.containerd.runc.v1(#8262)aufssnapshotter (#8263)Deprecations
Please try out the release binaries and report any issues at
https://github.com/containerd/containerd/issues.
Contributors
Dependency Changes
1f10f66->e8a1dd75330a85->2b5cbb2ea5083fnewd8f796aa7dc8b6newcca7078new3a7f492-> v1.1.0946c877->2e043c65d4384e78d3cae->78284952eb08e3-> v0.0.4686a1a2new432b235-> v0.9.0aacd6d4new90d013b-> v0.3.05fefd90new324edc3newa5ecb01->18e509bf223a00->bc3834cPrevious release can be found at v1.7.0
Which file should I download?
containerd-<VERSION>-<OS>-<ARCH>.tar.gz: ✅Recommended. Dynamically linked with glibc 2.31 (Ubuntu 20.04).containerd-static-<VERSION>-<OS>-<ARCH>.tar.gz: Statically linked. Expected to be used on non-glibc Linux distributions. Not position-independent.In addition to containerd, typically you will have to install runc
and CNI plugins from their official sites too.
See also the Getting Started documentation.
v1.7.35: containerd 1.7.35Compare Source
Welcome to the v1.7.35 release of containerd!
The thirty-fifth patch release for containerd 1.7 contains various fixes
and updates including security patches.
Security Updates
Highlights
Image Distribution
Runtime
Please try out the release binaries and report any issues at
https://github.com/containerd/containerd/issues.
Contributors
Changes
13 commits
05aa78da3Prepare release notes for v1.7.353bd79bb36Merge commit from fork5a2a3a759cri: cancel ExecSync IO drain on context cancellation323e148f2Merge commit from fork9205b1903archive: skip redundant opaque whiteout walksb01d66349core/remotes/docker: normalize descriptor URL originsb5d936dcacore/remotes/docker: strip sensitive headers on desc.urls fetchcff94ea40ctr: add --scrub-logs flag for Windows544e4657dcri/config: use ScrubLogs by default on Windows71e00ba9cci: bound Go fuzzing by execution countDependency Changes
This release has no dependency changes
Previous release can be found at v1.7.34
v1.7.34: containerd 1.7.34Compare Source
Welcome to the v1.7.34 release of containerd!
The thirty-fourth patch release for containerd 1.7 contains various fixes and updates.
Highlights
Container Runtime Interface (CRI)
Please try out the release binaries and report any issues at
https://github.com/containerd/containerd/issues.
Contributors
Changes
5 commits
7db112471Prepare release notes for v1.7.34c06144c85Update go to 1.26.5/1.25.12b84460e50ci: pin fog-json to resolve gem conflict2fe076ea7cri:fix lost container exit events if they arrive before info is cached862057716bump golang.org/x/* dependenciesDependency Changes
Previous release can be found at v1.7.33
v1.7.33: containerd 1.7.33Compare Source
Welcome to the v1.7.33 release of containerd!
The thirty-third patch release for containerd 1.7 contains various fixes
and updates including security patches.
Security Updates
containerd
go-jose
Please try out the release binaries and report any issues at
https://github.com/containerd/containerd/issues.
Contributors
Changes
17 commits
7517e6737Prepare release notes for v1.7.33ab306518aMerge commit from forkd34cdafdaMerge commit from fork9ab2b7a89Bound user-database file reads in openBoundedUserFile1e9806f90Merge commit from fork4d8ba4d23Do not propagate reserved labels from image configs74c728c13update runc binary to v1.3.6947caa4b7update go to 1.26.4/1.25.11e884e964eConfigure udevd children-max for root-testb9e756888Clean up disk space in node e2e workflow4dfc1844e](https://redirect.github.com/containerd/containerd/commit/4dfc1844e8cb46a6c04a8c57211abConfiguration
📅 Schedule: Branch creation - "" in timezone Asia/Shanghai, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.