Affected by GO-2025-3528
and 7 other vulnerabilities
GO-2025-3528: containerd has an integer overflow in User ID handling in github.com/containerd/containerd
GO-2025-4100: containerd affected by a local privilege escalation via wide permissions on CRI directory in github.com/containerd/containerd
GO-2025-4108: containerd CRI server: Host memory exhaustion through Attach goroutine leak in github.com/containerd/containerd
GO-2026-5064: containerd CRI checkpoint restore CDI annotation smuggling in github.com/containerd/containerd
GO-2026-5338: containerd: CRI checkpoint import allows local image tag poisoning in github.com/containerd/containerd
GO-2026-5475: containerd image-triggered runtime DoS via unbounded group parsing in github.com/containerd/containerd
GO-2026-5622: Arbitrary host CRI log file read via symlink following in CRI checkpoint restore in github.com/containerd/containerd
GO-2026-5758: containerd CRI — image-config `LABEL` flows to restart-monitor `binary://` logger: host-root command execution from an image pull in github.com/containerd/containerd
FileInfoHeaderNoLookups creates a partially-populated tar.Header from fi.
Compared to the archive/tar.FileInfoHeader function, this function is safe to
call from a chrooted process as it does not populate fields which would
require operating system lookups. It behaves identically to
tar.FileInfoHeader when fi is a FileInfo value returned from
tar.Header.FileInfo().
When fi is a FileInfo for a native file, such as returned from os.Stat() and
os.Lstat(), the returned Header value differs from one returned from
tar.FileInfoHeader in the following ways. The Uname and Gname fields are not
set as OS lookups would be required to populate them. The AccessTime and
ChangeTime fields are not currently set (not yet implemented) although that
is subject to change. Callers which require the AccessTime or ChangeTime
fields to be zeroed should explicitly zero them out in the returned Header
value to avoid any compatibility issues in the future.