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

helm

Helm

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

Lifecycle evidence status

Official registry publication history is available at helm, but registry activity is not a publisher support boundary.

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-63308 17 Jul 2026 ≤ 4.2.3 ba6c9a29efa7bf9198dad6a5ec12b4fb30c96017 Update reference ↗
CVE-2026-35206 9 Apr 2026 >= 4.0.0, < 4.1.4; < 3.20.2 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-2026-35205 9 Apr 2026 >= 4.0.0, < 4.1.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-2026-35204 9 Apr 2026 >= 4.0.0, < 4.1.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-2025-55198 13 Aug 2025 < 3.18.5 For OpenShift Container Platform 4.20 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.redhat.com/en/documentation/openshift_container_platform/4.20/html/release_notes/ You may download the oc tool and use it to inspect release image metadata for x86_64, s390x, ppc64le, and aarch64 architectures. The image digests may be found at https://quay.io/repository/openshift-release-dev/ocp-release?tab=tags. The sha values for the release are as follows: (For x86_64 architecture) The image digest is sha256:a29bcbc9f286d68b394ffa0288c5de7e487c90077c06cbaf7a4cadeb0398ce28 (For s390x architecture) The image digest is sha256:724ea94541fa32defeae6a782fb2f1194e5bd7221ec33d7bcc6c4dc1e53cabc3 (For ppc64le architecture) The image digest is sha256:125ba716fa99fd8dbf33a8407030ad06704cd394dfc4898f7d6fb69e1bc9a8cd (For aarch64 architecture) The image digest is sha256:38a6732d5a3485f145657156e3c0625c21aa0af16c49959dd97eec75bfb1706e All OpenShift Container Platform 4.20 users are advised to upgrade to these updated packages and images when they are available in the appropriate release channel. To check for available updates, use the OpenShift CLI (oc) or web console. Instructions for upgrading a cluster are available at https://docs.redhat.com/en/documentation/openshift_container_platform/4.20/html-single/updating_clusters/index#updating-cluster-cli. Update reference ↗
CVE-2025-55199 13 Aug 2025 < 3.18.5 For OpenShift Container Platform 4.20 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.redhat.com/en/documentation/openshift_container_platform/4.20/html/release_notes/ You may download the oc tool and use it to inspect release image metadata for x86_64, s390x, ppc64le, and aarch64 architectures. The image digests may be found at https://quay.io/repository/openshift-release-dev/ocp-release?tab=tags. The sha values for the release are as follows: (For x86_64 architecture) The image digest is sha256:a29bcbc9f286d68b394ffa0288c5de7e487c90077c06cbaf7a4cadeb0398ce28 (For s390x architecture) The image digest is sha256:724ea94541fa32defeae6a782fb2f1194e5bd7221ec33d7bcc6c4dc1e53cabc3 (For ppc64le architecture) The image digest is sha256:125ba716fa99fd8dbf33a8407030ad06704cd394dfc4898f7d6fb69e1bc9a8cd (For aarch64 architecture) The image digest is sha256:38a6732d5a3485f145657156e3c0625c21aa0af16c49959dd97eec75bfb1706e All OpenShift Container Platform 4.20 users are advised to upgrade to these updated packages and images when they are available in the appropriate release channel. To check for available updates, use the OpenShift CLI (oc) or web console. Instructions for upgrading a cluster are available at https://docs.redhat.com/en/documentation/openshift_container_platform/4.20/html-single/updating_clusters/index#updating-cluster-cli. Update reference ↗
CVE-2025-53547 8 Jul 2025 < 3.18.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://access.redhat.com/articles/11258 https://access.redhat.com/security/updates/classification/#important Update reference ↗
CVE-2025-32386 9 Apr 2025 < 3.17.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-2025-32387 9 Apr 2025 < 3.17.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-2024-26147 21 Feb 2024 < 3.14.2 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 Update reference ↗
CVE-2024-25620 14 Feb 2024 < 3.14.1 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 Update reference ↗
CVE-2023-25165 8 Feb 2023 >= 3.0.0, < 3.11.1 For OpenShift Container Platform 4.12 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/4.12/release_notes/ocp-4-12-release-notes.html You can download the oc tool and use it to inspect release image metadata for x86_64, s390x, ppc64le, and aarch64 architectures. The image digests can be found at https://quay.io/repository/openshift-release-dev/ocp-release?tab=tags. The sha values for the release are: (For x86_64 architecture) The image digest is sha256:b584f5458fb946115b0cf0f1793dc9224c5e6a4567e74018f0590805a03eb523 (For s390x architecture) The image digest is sha256:ae75a168532559fb36fe42cff4add4ac45d8ae20a13b0dc468350d5857d3a3bc (For ppc64le architecture) The image digest is sha256:fa90a8f095f747bd8bfd1778948205fa0a1d0326d48612d1397a613d6e481ea6 (For aarch64 architecture) The image digest is sha256:e48f462cee06aeadd854ea39e3a6c6bba6ee223bc4d3686d00acd78e4f19d209 All OpenShift Container Platform 4.12 users are advised to upgrade to these updated packages and images when they are available in the appropriate release channel. To check for available updates, use the OpenShift CLI (oc) or web console. Instructions for upgrading a cluster are available at https://docs.openshift.com/container-platform/4.12/updating/updating-cluster-cli.html Update reference ↗
CVE-2022-23526 15 Dec 2022 < v3.10.3 For OpenShift Container Platform 4.12 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/4.12/release_notes/ocp-4-12-release-notes.html Update reference ↗
CVE-2022-23525 15 Dec 2022 < v3.10.3 For OpenShift Container Platform 4.12 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/4.12/release_notes/ocp-4-12-release-notes.html Update reference ↗
CVE-2022-23524 15 Dec 2022 < v3.10.3 To take advantage of the new features, bug fixes, and enhancements in RHACS 4.0, you are advised to upgrade to RHACS 4.0. Update reference ↗
CVE-2022-36055 1 Sep 2022 < 3.9.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-32690 16 Jun 2021 < 3.6.1 To take advantage of these new features, fixes and changes, please upgrade Red Hat Advanced Cluster Security for Kubernetes to version 3.67. Update reference ↗
CVE-2021-21303 5 Feb 2021 > 3.0, < 3.5.2 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-15187 17 Sep 2020 >= 2.0.0, < 2.16.11; >= 3.0.0, < 3.3.2 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-15186 17 Sep 2020 >= 2.0.0, < 2.16.11; >= 3.0.0, < 3.3.2 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-15185 17 Sep 2020 >= 2.0.0, < 2.16.11; >= 3.0.0, < 3.3.2 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-15184 17 Sep 2020 >= 2.0.0, < 2.16.11; >= 3.0.0, < 3.3.2 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-11013 24 Apr 2020 >= 3.1.0, < 3.2.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-1010275 17 Jul 2019 Before 2.7.2 [fixed: 2.7.2] 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 ↗

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.