Evidence-linked product lifecycle intelligenceSUPPORT · SECURITY · RETIREMENT
← Search results
CVE-LINKED INVENTORY24 SECURITY RECORDS

containerd

containerd

Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.

Lifecycle evidence status

This CVE identity is linked to the Lifecycle record containerd. Use that record for publisher support phases and retirement dates.

A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.

CVE-observed version history

CVEPublishedAffected versionsFixed version informationPublisher evidence
CVE-2026-53493 25 Sep 2026 containerd: >= 2.0.0, < 2.0.13, < 1.7.36, >= 2.1.0, < 2.2.9, >= 2.3.0, < 2.3.6, = 2.4.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-53495 14 Sep 2026 containerd: < 1.7.35, >= 2.0.0, < 2.0.12, >= 2.2.0, < 2.2.8, >= 2.3.0, < 2.3.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-53489 1 Jul 2026 >= 2.1.0, < 2.1.9; >= 2.2.0, < 2.2.5; >= 2.3.0, < 2.3.2 For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/ Update reference ↗
CVE-2026-53492 1 Jul 2026 >= 2.1.0, < 2.1.9; >= 2.2.0, < 2.2.5; >= 2.3.0, < 2.3.2 For more details, see the Red Hat Advanced Cluster Management for Kubernetes documentation: https://docs.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.13/html/multicluster_global_hub/index Update reference ↗
CVE-2026-50195 1 Jul 2026 >= 2.1.0, < 2.1.9; >= 2.2.0, < 2.2.5; >= 2.3.0, < 2.3.2 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-47262 1 Jul 2026 >= 1.7.0, < 1.7.33; >= 2.0.0, < 2.0.10; >= 2.1.0, < 2.1.9; >= 2.2.0, < 2.2.5; >= 2.3.0, < 2.3.2 For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/ Update reference ↗
CVE-2026-46680 1 Jul 2026 < 1.7.32; >= 2.0.4, < 2.0.9; >= 2.0.10, < 2.2.4; >= 2.2.5, < 2.3.1 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-53488 1 Jul 2026 < 1.7.33; >= 2.0.0, < 2.0.10; >= 2.1.0, < 2.1.9; >= 2.2.0, < 2.2.5; >= 2.3.0, < 2.3.2 For more details, see the Red Hat Advanced Cluster Management for Kubernetes documentation: https://docs.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.13/html/multicluster_global_hub/index Update reference ↗
CVE-2025-64329 7 Nov 2025 < 1.7.29; < 2.0.7; >= 2.1.0-beta.0, < 2.1.5; >= 2.2.0-beta.0, < 2.2.0 For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 Update reference ↗
CVE-2024-25621 6 Nov 2025 < 1.7.29; >= 2.0.0-beta.0, < 2.0.7; >= 2.1.0-beta.0, < 2.1.5; >= 2.2.0-beta.0, < 2.2.0 For more details, see the Red Hat Advanced Cluster Management for Kubernetes documentation: https://docs.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.13/html/multicluster_global_hub/index Update reference ↗
CVE-2025-47291 21 May 2025 >= 2.0.1, < 2.0.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-47290 20 May 2025 = 2.1.0 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2024-40635 17 Mar 2025 < 1.6.38; >= 1.7.0-beta.0, < 1.7.27; >= 2.0.0-beta.0, < 2.0.4 Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://docs.redhat.com/en/documentation/red_hat_openshift_data_foundation/4.22/html/updating_openshift_data_foundation/updating-ocs-to-odf_rhodf Update reference ↗
CVE-2023-25173 16 Feb 2023 < 1.5.18; >= 1.6.0, < 1.6.18 For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 Update reference ↗
CVE-2023-25153 16 Feb 2023 < 1.5.18; >= 1.6.0, < 1.6.18 Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 For supported configurations, refer to: https://access.redhat.com/articles/1548993 Update reference ↗
CVE-2022-23471 7 Dec 2022 < 1.5.16; >= 1.6.0, < 1.6.12 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2022-31030 6 Jun 2022 < 1.5.13; >= 1.6.0, < 1.6.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-23648 3 Mar 2022 < 1.4.13; >= 1.5.0, < 1.5.10; >= 1.6.0, < 1.6.1 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2021-43816 5 Jan 2022 >= 1.5.0, < 1.5.9 1.5.9. Update reference ↗
CVE-2021-41103 4 Oct 2021 < 1.4.11; >= 1.5.0, < 1.5.7 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2021-32760 19 Jul 2021 <= 1.4.7; >= 1.5.0, <= 1.5.3 OSP 16.2 Release - OSP Director Operator Containers tech preview Update reference ↗
CVE-2021-21334 10 Mar 2021 < 1.3.10; >= 1.4.0, < 1.4.4 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2020-15257 1 Dec 2020 < 1.3.9; >= 1.4.0, < 1.4.3 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2020-15157 16 Oct 2020 < 1.2.14 No fixed version is explicitly recorded in the structured CVE data. Use CVE record

How this record is maintained

The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.