github.com/containerd/containerd v1.7.34
PkgFire would install this release with a warning.·Checked 12 hours ago·Published 9 July 2026
Why
-
warnVulnerability
containerd CRI checkpoint restore CDI annotation smuggling in github.com/containerd/containerd
-
warnVulnerability
containerd: CRI checkpoint import allows local image tag poisoning in github.com/containerd/containerd
-
warnVulnerability
Arbitrary host CRI log file read via symlink following in CRI checkpoint restore in github.com/containerd/containerd
-
warnVulnerability
containerd: CRI ExecSync Goroutine Leak Leads to Node-Level Denial of Service in github.com/containerd/containerd (fixed in 1.7.35)
-
warnVulnerability
Containerd has image-pull DoS via crafted OCI index graph amplification in github.com/containerd/containerd (fixed in 1.7.36)
-
warnVulnerability
containerd CRI plugin: Checkpoint restore bypasses destination security context in github.com/containerd/containerd
-
warnVulnerability
containerd: Unpack DoS via repeated opaque whiteouts in github.com/containerd/containerd (fixed in 1.7.35)
-
warnVulnerability
containerd: CRI ExecSync Goroutine Leak Leads to Node-Level Denial of Service (fixed in 1.7.35)
-
warnVulnerability
Containerd has image-pull DoS via crafted OCI index graph amplification (fixed in 1.7.36)
-
warnVulnerability
containerd: Unpack DoS via repeated opaque whiteouts (fixed in 1.7.35)
What the code does
On its own this is weak signal: plenty of honest libraries read files or talk to the network. What PkgFire watches is a release gaining something the one before it did not.
Source patterns
Patterns found in the source, including those malware is known to use.
Other checked releases
Check every dependency before it installs
This page is one release. PkgFire checks every package in your lockfile, on every install and in every pull request, and blocks the bad ones before they run.