https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-03T22:50:49.366995+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bdu:2023-00284 bdu:2023-00284 2026-10-03T22:50:49.538315+00:00 bdu:2023-00284 https://cve.radiocsirt.org/vuln/bell-cve-2021-21334 Withdrawn: BELL-CVE-2021-21334 — CVE-2021-21334 does not affect BellSoft software 2026-10-03T22:50:49.538384+00:00

Withdrawn by the publisher.

https://cve.radiocsirt.org/vuln/certfr-2022-avi-624 certfr-2022-avi-624 — De multiples vulnérabilités ont été découvertes dans IBM MQ Operator et Queue manager. Elles permettent à un attaquant… 2026-10-03T22:50:49.538415+00:00 certfr-2022-avi-624 https://cve.radiocsirt.org/vuln/cleanstart-2025-bs91981 CLEANSTART-2025-BS91981 — In containerd (an industry-standard container runtime) before versions 1 2026-10-03T22:50:49.538439+00:00

Affected: CleanStart: containerd

Security vulnerability affects the containerd package. In containerd (an industry-standard container runtime) before versions 1.

 https://cve.radiocsirt.org/vuln/euvd-2026-22126 EUVD-2026-22126 2026-10-03T22:50:49.538478+00:00 EUVD-2026-22126 https://cve.radiocsirt.org/vuln/fkie_cve-2021-21334 fkie_cve-2021-21334 2026-10-03T22:50:49.538496+00:00

In containerd (an industry-standard container runtime) before versions 1.3.10 and 1.4.4, containers launched through containerd's CRI implementation (through Kubernetes, crictl, or any other pod/container client that uses the containerd CRI service) that share the same image may receive incorrect environment variables, including values that are defined for other containers. If the affected containers have different security contexts, this may allow sensitive information to be unintentionally shared. If you are not using containerd's CRI implementation (through one of the mechanisms described above), you are not vulnerable to this issue. If you are not launching multiple containers or Kubernetes pods from the same image which have different environment variables, you are not vulnerable to this issue. If you are not launching multiple containers or Kubernetes pods from the same image in rapid succession, you have reduced likelihood of being vulnerable to this issue This vulnerability has been fixed in containerd 1.3.10 and containerd 1.4.4. Users should update to these versions.

 https://cve.radiocsirt.org/vuln/ghsa-6g2q-w5j3-fwh4 GHSA-6g2q-w5j3-fwh4 — containerd environment variable leak 2026-10-03T22:50:49.538537+00:00

Affected: Go: github.com/containerd/containerd

## Impact

Containers launched through containerd's CRI implementation (through Kubernetes, crictl, or any other pod/container client that uses the containerd CRI service) that share the same image may receive incorrect environment variables, including values that are defined for other containers. If the affected containers have different security contexts, this may allow sensitive information to be unintentionally shared.

If you are not using containerd’s CRI implementation (through one of the mechanisms described above), you are not vulnerable to this issue.

If you are not launching multiple containers or Kubernetes pods from the same image which have different environment variables, you are not vulnerable to this issue.

If you are not launching multiple containers or Kubernetes pods from the same image in rapid succession, you have reduced likelihood of being vulnerable to this issue

## Patches

This vulnerability has been fixed in containerd 1.3.10 and containerd 1.4.4. Users should update to these versions as soon as they are released.

## Workarounds

There are no known workarounds.

## For more information

If you have any questions or comments about this advisory:

* [Open an issue](https://github.com/containerd/containerd/issues/new/choose) * Email us at security@containerd.io if you think you’ve found a security bug.

 https://cve.radiocsirt.org/vuln/gsd-2021-21334 gsd-2021-21334 2026-10-03T22:50:49.538602+00:00 gsd-2021-21334 https://cve.radiocsirt.org/vuln/msrc_cve-2021-21334 msrc_CVE-2021-21334 — environment variable leak 2026-10-03T22:50:49.538620+00:00 msrc_CVE-2021-21334 https://cve.radiocsirt.org/vuln/opensuse-su-2024:10693-1 openSUSE-SU-2024:10693-1 — containerd-1.4.8-2.2 on GA media 2026-10-03T22:50:49.538644+00:00

containerd-1.4.8-2.2 on GA media

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-21334 UBUNTU-CVE-2021-21334 2026-10-03T22:50:49.538672+00:00

Affected: Ubuntu:Pro:16.04:LTS: containerd, Ubuntu:18.04:LTS: containerd, Ubuntu:20.04:LTS: containerd

In containerd (an industry-standard container runtime) before versions 1.3.10 and 1.4.4, containers launched through containerd's CRI implementation (through Kubernetes, crictl, or any other pod/container client that uses the containerd CRI service) that share the same image may receive incorrect environment variables, including values that are defined for other containers. If the affected containers have different security contexts, this may allow sensitive information to be unintentionally shared. If you are not using containerd's CRI implementation (through one of the mechanisms described above), you are not vulnerable to this issue. If you are not launching multiple containers or Kubernetes pods from the same image which have different environment variables, you are not vulnerable to this issue. If you are not launching multiple containers or Kubernetes pods from the same image in rapid succession, you have reduced likelihood of being vulnerable to this issue This vulnerability has been fixed in containerd 1.3.10 and containerd 1.4.4. Users should update to these versions.

 https://cve.radiocsirt.org/vuln/wid-sec-w-2022-1002 WID-SEC-W-2022-1002 — Amazon Linux 2: Mehrere Schwachstellen 2026-10-03T22:50:49.538716+00:00

Ein lokaler Angreifer kann mehrere Schwachstellen in Amazon Linux 2 ausnutzen, um Informationen offenzulegen, Dateien zu manipulieren oder falsche Informationen darzustellen.