chore(deps): update module github.com/containerd/containerd to v1.7.33 [security] - #198
Open
alaudaa-renovate[bot] wants to merge 1 commit into
Open
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
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->v1.7.33Warning
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:
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 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 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 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)
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 workflow4dfc1844eBump go-jose to v3.0.5 to address CVE-2026-34986Dependency Changes
Previous release can be found at v1.7.32
v1.7.32: containerd 1.7.32Compare Source
Welcome to the v1.7.32 release of containerd!
The thirty-second patch release for containerd 1.7 contains various fixes
and updates including a security patch.
containerd
Allow hosts.toml to contain only root-level fields without an explicit [host] section (#10028)
Fix handling of out-of-range USER values in OCI spec to avoid unexpected username/group lookups (#13450)
Apply hardening to block AF_ALG in default socket policy (#13406)
Support both "volatile" and "fsync=volatile" mount options for volatile snapshotter (#13299)
Set AppArmor abi conditionally to support versions < 3.0 (#13273)
Please try out the release binaries and report any issues at
https://github.com/containerd/containerd/issues.
17 commits
bc87d865cPrepare release notes for v1.7.32503f47946oci: return explicit error for out-of-range USER valuese55b747d3seccomp: Block AF_ALG in default socket policy4627a65f8seccomp: Document socket rule scope and socketcall limitation24007441dFix error parsing hosts.toml without anyhosttree940733149Support both styles of volatile mount option2b732c892apparmor: Set abi conditionally0db1e143aAdd GitHub Action for k8s node e2e tests3223a75c2Update for latest updates to release tool1b30082ebUpdate release process after 1.7This release has no dependency changes
Previous release can be found at v1.7.31
v1.7.31: containerd 1.7.31Compare Source
Welcome to the v1.7.31 release of containerd!
The thirty-first patch release for containerd 1.7 contains various fixes
and updates including a security patch.
Security 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
37 commits
7d2662653Prepare release notes for v1.7.313f795c02aupdate github.com/moby/spdystream v0.5.17b1e1b17bupdate to Go 1.25.9, 1.26.2b673f2d42update golangci-lint to v2.9.0 with go1.26 supportd88d8513aremove windows/arm from cross builda763407b5Ignore warnings for golangci-lint bump03dcd8360ci: bump golangci from 6.5.2 to 7.0.0c08711218Update github.com/moby/spdystream v0.2.0->v0.5.0043548f6dSkip TestExportAndImportMultiLayer on s390xe99bd6050[release/1.7] update runc binary to v1.3.53a3103aafCODEOWNERS: mark Sam and Chris as owners for 1.79b4cfa271Ignore NOCHANGE error53e9e73f0ci: modprobe xt_comment on almalinux61c2733fdFix TOCTOU race bug in tar extractionf854c1890fix issue where cni del is never executed5c091d92eapparmor: explicitly set abi/3.0177ac10feintegration: Fix TestImageLoad() failure on CI56da43d0fupdate to go1.24.13, go1.25.75cb3cb9baci: bump go 1.24.12, 1.25.6b1fa03843fix: sanitize error before gRPC return to prevent credential leak in pod eventse2c93a42ccri: emit warning for concurrent CreateContainerDependency Changes
Previous release can be found at v1.7.30
v1.7.30: containerd 1.7.30Compare Source
Welcome to the v1.7.30 release of containerd!
The thirtieth patch release for containerd 1.7 contains various fixes
and updates.
Highlights
Container Runtime Interface (CRI)
Runtime
Please try out the release binaries and report any issues at
https://github.com/containerd/containerd/issues.
Contributors
Changes
26 commits
3d0ca6d2ePrepare release notes for v1.7.300bc74f47ecri,nri: don't drop requested CDI devices silently.7db16b562script/setup/install-cni: install CNI plugins v1.9.0bca897b47go.mod: golang.org/x/crypto v0.45.037cbd2224CI: drop Go 1.23ee49d1747Update Go requirements in BUILDING145978224ci: bump Go 1.24.11, 1.25.53dbadfaa1ci: bump Go 1.24.10, 1.25.42bac971f0ci(release): set GO_VERSION in Dockerfile34b89a574runc: Update runc binary to v1.3.46e0dd8956ci: update CIFuzz actions to support Ubuntu 24.043eea2a4afbuild(deps): bump github.com/opencontainers/selinux1194f5128remove sha256-simdce2d3a67f.github: skip 5 critest cases in window CI pipeline65271ea89fix: redact all query parameters in CRI error logsDependency Changes
Previous release can be found at v1.7.29
Configuration
📅 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.