https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-02T12:59:53.047547+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bell-cve-2026-53492 BELL-CVE-2026-53492 2026-10-02T12:59:53.368404+00:00

Affected: Alpaquita:25: containerd, Alpaquita:stream: containerd

 https://cve.radiocsirt.org/vuln/cleanstart-2026-bs31967 Withdrawn: CLEANSTART-2026-BS31967 — Security fixes in rancher-fleet-agent 0.13.13-r1 2026-10-02T12:59:53.368492+00:00

Withdrawn by the publisher.

Affected: CleanStart: rancher-fleet-agent

Package rancher-fleet-agent version 0.13.13-r1 fixes 34 vulnerabilities: CVE-2026-50195, CVE-2026-53492, CVE-2026-46680, CVE-2026-53488, CVE-2026-53489...

 https://cve.radiocsirt.org/vuln/euvd-2026-332259 EUVD-2026-332259 2026-10-02T12:59:53.368522+00:00 EUVD-2026-332259 https://cve.radiocsirt.org/vuln/fkie_cve-2026-53492 fkie_cve-2026-53492 2026-10-02T12:59:53.368536+00:00

containerd is an open-source container runtime. In Versions prior to 2.3.2, 2.2.5 and 2.1.9, the CRI implementation improperly trusts Container Device Interface (CDI) annotations found within untrusted checkpoint image metadata during container restoration. When restoring a container from a checkpoint, containerd preserves CDI-related annotations from the checkpoint archive rather than relying solely on the pod's create-time specification. This allows a user with pod creation permissions to bypass standard Kubernetes resource allocation and device plugin enforcement, injecting arbitrary CDI edits (such as device nodes and host mounts) into the restored container. Successful exploitation requires that the node has CDI enabled and contains a matching host CDI specification for the requested device; environments where CDI is disabled or lacking sensitive device specifications are not affected. This issue has been fixed in versions 2.3.2, 2.2.5 and 2.1.9.

 https://cve.radiocsirt.org/vuln/ghsa-33vj-92qq-66hc GHSA-33vj-92qq-66hc — containerd CRI checkpoint restore CDI annotation smuggling 2026-10-02T12:59:53.368565+00:00

Affected: Go: github.com/containerd/containerd/v2

### Impact

containerd's CRI implementation improperly trusts Container Device Interface (CDI) annotations found within untrusted checkpoint image metadata during container restoration. When restoring a container from a checkpoint, containerd preserves CDI-related annotations from the checkpoint archive rather than relying solely on the pod's create-time specification. This allows a user with pod creation permissions to bypass standard Kubernetes resource allocation and device plugin enforcement, injecting arbitrary CDI edits (such as device nodes and host mounts) into the restored container. Successful exploitation requires that the node has CDI enabled and contains a matching host CDI specification for the requested device; environments where CDI is disabled or lacking sensitive device specifications are not affected.

### Patches

This bug has been fixed in the following containerd versions:

* 2.3.2 * 2.2.5 * 2.1.9

Users should update to these versions to resolve the issue. Recreating existing containers restored from untrusted checkpoints may be necessary to remove smuggled configuration.

### Workarounds

Users can mitigate this issue by restricting the restoration of containers from untrusted checkpoint images. If Container Device Interface (CDI) capabilities are not utilized on the node, removing or temporarily relocating host CDI specifications from the default directories (`/etc/cdi` and `/var/run/cdi`) will eliminate the reachability of this vulnerability.

### C…

 https://cve.radiocsirt.org/vuln/opensuse-su-2026:11102-1 openSUSE-SU-2026:11102-1 — trivy-0.71.2-1.1 on GA media 2026-10-02T12:59:53.368624+00:00

trivy-0.71.2-1.1 on GA media

 https://cve.radiocsirt.org/vuln/rhsa-2026:15862 RHSA-2026:15862 — Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update 2026-10-02T12:59:53.368646+00:00

github.com/quic-go/quic-go: quic-go: Denial of Service via excessive memory allocation in HTTP/3 trailers urllib3: urllib3: Denial of Service due to excessive HTTP response decompression go.opentelemetry.io/otel: go.opentelemetry.io/otel/schema/v1.0: go.opentelemetry.io/otel/schema/v1.1: OpenTelemetry-Go: Denial of Service due to file descriptor leak github.com/containerd/containerd: containerd: Arbitrary host file read via symlink following in CRI checkpoint restore github.com/containerd/containerd: containerd: Security bypass via Container Device Interface (CDI) annotation smuggling during checkpoint restoration.

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-53492 UBUNTU-CVE-2026-53492 2026-10-02T12:59:53.368671+00:00

Affected: Ubuntu:22.04:LTS: containerd-app, Ubuntu:24.04:LTS: containerd-app, Ubuntu:25.10: containerd-app, Ubuntu:25.10: containerd-stable, Ubuntu:26.04:LTS: containerd-app, Ubuntu:26.04:LTS: containerd-stable

containerd is an open-source container runtime. In Versions prior to 2.3.2, 2.2.5 and 2.1.9, the CRI implementation improperly trusts Container Device Interface (CDI) annotations found within untrusted checkpoint image metadata during container restoration. When restoring a container from a checkpoint, containerd preserves CDI-related annotations from the checkpoint archive rather than relying solely on the pod's create-time specification. This allows a user with pod creation permissions to bypass standard Kubernetes resource allocation and device plugin enforcement, injecting arbitrary CDI edits (such as device nodes and host mounts) into the restored container. Successful exploitation requires that the node has CDI enabled and contains a matching host CDI specification for the requested device; environments where CDI is disabled or lacking sensitive device specifications are not affected. This issue has been fixed in versions 2.3.2, 2.2.5 and 2.1.9.

 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2009 WID-SEC-W-2026-2009 — Google Cloud Platform (GKE containerd): Mehrere Schwachstellen 2026-10-02T12:59:53.368704+00:00

Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in Google Cloud Platform ausnutzen, um beliebigen Programmcode auszuführen, Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren, vertrauliche Informationen offenzulegen oder einen Denial-of-Service-Zustand zu verursachen.