BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2025-55198High confidence

Helm May Panic Due To Incorrect YAML Content

helm · helm

Official source article: GitHub GHSA-F9F8-9PMF-XV68 ↗. Check the applicable product and release in the original source.

6.5MediumCVSS 3.1
Recommended action
Scheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Medium, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.33% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs helm helm and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Open-source package ranges2 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
Gohelm.sh/helm/v3SEMVER: introduced 0; fixed 3.18.53.18.5OSV record ↗aggregator derived · 10 Sep 2026
gohelm.sh/helm/v3< 3.18.53.18.5GitHub advisory ↗upstream repository advisory · 14 Aug 2025
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2025-55198 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityhelm.sh/helm/v3: Helm YAML Parsing Panic Vulnerability
97 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • dvo/deployment-validation-rhel8-operator as a component of Deployment Validation Operator
  • mta/mta-cli-rhel9 as a component of Migration Toolkit for Applications 7
  • multicluster-engine/addon-manager-rhel8 as a component of Multicluster Engine for Kubernetes
  • multicluster-engine/addon-manager-rhel9 as a component of Multicluster Engine for Kubernetes
  • multicluster-engine/backplane-rhel8-operator as a component of Multicluster Engine for Kubernetes
  • multicluster-engine/backplane-rhel9-operator as a component of Multicluster Engine for Kubernetes
  • multicluster-engine/cluster-proxy-rhel8 as a component of Multicluster Engine for Kubernetes
  • multicluster-engine/cluster-proxy-rhel9 as a component of Multicluster Engine for Kubernetes
  • multicluster-engine/hypershift-addon-rhel8-operator as a component of Multicluster Engine for Kubernetes
  • multicluster-engine/hypershift-addon-rhel9-operator as a component of Multicluster Engine for Kubernetes
  • multicluster-engine/managed-serviceaccount-rhel8 as a component of Multicluster Engine for Kubernetes
  • multicluster-engine/managed-serviceaccount-rhel9 as a component of Multicluster Engine for Kubernetes
Summary
A flaw was found in helm.sh/helm/v3. Improper validation of type errors during parsing of Chart.yaml and index.yaml files can trigger a panic. A remote attacker, requiring user interaction, can trigger this panic via a malformed chart file. This can lead to an application level denial of service.
Remediation
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.
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2025-24646

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
01

What, why and how

Helm is a package manager for Charts for Kubernetes. Prior to version 3.18.5, when parsing Chart.yaml and index.yaml files, an improper validation of type error can lead to a panic. This issue has been resolved in Helm 3.18.5. A workaround involves ensuring YAML files are formatted as Helm expects prior to processing them with Helm.

What

Helm is a package manager for Charts for Kubernetes. Prior to version 3.18.5, when parsing Chart.yaml and index.yaml files, an improper validation of type error can lead to a panic. This issue has been resolved in Helm 3.18.5. A workaround involves ensuring YAML files are formatted as Helm expects prior to processing them with Helm.

Why

The product uses or accesses a resource that has not been initialized.

How

An attacker operating through a network path may attempt exploitation without authentication after a user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

Helm is a package manager for Charts for Kubernetes. Prior to version 3.18.5, when parsing Chart.yaml and index.yaml files, an improper validation of type error can lead to a panic. This issue has been resolved in Helm 3.18.5. A workaround involves ensuring YAML files are formatted as Helm expects prior to processing them with Helm.

Why

The product uses or accesses a resource that has not been initialized.

How

An attacker operating through a network path may attempt exploitation without authentication after a user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Use of Uninitialized Resource → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
Required interaction required
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-908 ↗

CWE-908: Use of Uninitialized Resource. The product uses or accesses a resource that has not been initialized.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-908
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2025-2727Red Hat OpenShift Container Platform: Mehrere Schwachstellen ermöglichen Denial of Service

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Red Hat OpenShift Container Platform ausnutzen, um einen Denial of Service Angriff durchzuführen.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0218Multiples vulnérabilités dans les produits VMware

Record?id=CVE-2025-5222 Référence CVE CVE-2025-5244 https://www.cve.org/CVERecord?id=CVE-2025-5244 Référence CVE CVE-2025-5245 https://www.cve.org/CVERecord?id=CVE-2025-5245 Référence CVE CVE-2025-52565 https://www.cve.org/CVERecord?id=CVE-2025-52565 Référence CVE CVE-2025-52881 https://www.cve.org/CVERecord?id=CVE-2025-52881 Référence CVE CVE-2025-53057 https://www.cve.org/CVERecord?id=CVE-2025-53057 Référence CVE CVE-2025-53066 https://www.cve.org/CVERecord?id=CVE-2025-53066 Référence CVE CVE-2025-53864 https://www.cve.org/CVERecord?id=CVE-2025-53864 Référence CVE CVE-2025-55163 https://www.cve.org/CVERecord?id=CVE-2025-55163 Référence CVE CVE-2025-55198 https://www.cve.org/CVERecord?id=CVE-2025-55198 Référence CVE CVE-2025-55199 https://www.cve.org/CVERecord?id=CVE-2025-55199 Référence CVE CVE-2025-58056 https://www.cve.org/CVERecord?id=CVE-2025-58056 Référence CVE CVE-2025-58057 https://www.cve.org/CVERecord?id=CVE-2025-58057 Référence CVE CVE-2025-58058 https://www.cve.org/CVERecord?id=CVE-2025-58058 Référence CVE CVE-2025-58181 https://www.cve.org/CVERecord?id=CVE-2025-58181 Référence CVE CVE-2025-58183 https://www.cve.org/CVERecord?id=CVE-2025-58183 Référence CVE CVE-2025-58185 https://www.cve.org/CVERecord?id=CVE-2025-58185 Référence CVE CVE-2025-58186 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0112Multiples vulnérabilités dans les produits VMware

d?id=CVE-2025-48060 Référence CVE CVE-2025-48989 https://www.cve.org/CVERecord?id=CVE-2025-48989 Référence CVE CVE-2025-52565 https://www.cve.org/CVERecord?id=CVE-2025-52565 Référence CVE CVE-2025-52881 https://www.cve.org/CVERecord?id=CVE-2025-52881 Référence CVE CVE-2025-53057 https://www.cve.org/CVERecord?id=CVE-2025-53057 Référence CVE CVE-2025-53066 https://www.cve.org/CVERecord?id=CVE-2025-53066 Référence CVE CVE-2025-53547 https://www.cve.org/CVERecord?id=CVE-2025-53547 Référence CVE CVE-2025-54388 https://www.cve.org/CVERecord?id=CVE-2025-54388 Référence CVE CVE-2025-54410 https://www.cve.org/CVERecord?id=CVE-2025-54410 Référence CVE CVE-2025-55198 https://www.cve.org/CVERecord?id=CVE-2025-55198 Référence CVE CVE-2025-55199 https://www.cve.org/CVERecord?id=CVE-2025-55199 Référence CVE CVE-2025-55752 https://www.cve.org/CVERecord?id=CVE-2025-55752 Référence CVE CVE-2025-55754 https://www.cve.org/CVERecord?id=CVE-2025-55754 Référence CVE CVE-2025-58058 https://www.cve.org/CVERecord?id=CVE-2025-58058 Référence CVE CVE-2025-58181 https://www.cve.org/CVERecord?id=CVE-2025-58181 Référence CVE CVE-2025-58183 https://www.cve.org/CVERecord?id=CVE-2025-58183 Référence CVE CVE-2025-58185 https://www.cve.org/CVERecord?id=CVE-2025-58185 Référence CVE CVE-2025-58186 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-1131Multiples vulnérabilités dans les produits IBM

ecord?id=CVE-2025-47907 Référence CVE CVE-2025-47913 https://www.cve.org/CVERecord?id=CVE-2025-47913 Référence CVE CVE-2025-48734 https://www.cve.org/CVERecord?id=CVE-2025-48734 Référence CVE CVE-2025-50059 https://www.cve.org/CVERecord?id=CVE-2025-50059 Référence CVE CVE-2025-5187 https://www.cve.org/CVERecord?id=CVE-2025-5187 Référence CVE CVE-2025-53057 https://www.cve.org/CVERecord?id=CVE-2025-53057 Référence CVE CVE-2025-53066 https://www.cve.org/CVERecord?id=CVE-2025-53066 Référence CVE CVE-2025-5372 https://www.cve.org/CVERecord?id=CVE-2025-5372 Référence CVE CVE-2025-55182 https://www.cve.org/CVERecord?id=CVE-2025-55182 Référence CVE CVE-2025-55198 https://www.cve.org/CVERecord?id=CVE-2025-55198 Référence CVE CVE-2025-55199 https://www.cve.org/CVERecord?id=CVE-2025-55199 Référence CVE CVE-2025-58057 https://www.cve.org/CVERecord?id=CVE-2025-58057 Référence CVE CVE-2025-58187 https://www.cve.org/CVERecord?id=CVE-2025-58187 Référence CVE CVE-2025-58188 https://www.cve.org/CVERecord?id=CVE-2025-58188 Référence CVE CVE-2025-58754 https://www.cve.org/CVERecord?id=CVE-2025-58754 Référence CVE CVE-2025-5914 https://www.cve.org/CVERecord?id=CVE-2025-5914 Référence CVE CVE-2025-59250 https://www.cve.org/CVERecord?id=CVE-2025-59250 Référence CVE CVE-2025-59375 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2025-012220Helm における初期化されていないリソースの使用に関する脆弱性

Helm には、初期化されていないリソースの使用に関する脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
Fixed
Action
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.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 13 Aug 2025 · Last source change 14 Aug 2025, 14:50 UTC · CWE-908 · Use of Uninitialized Resource

CVE recordCVE.org · 5.1
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2025-24646
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    < 3.18.5 · Fixed: For OpenShift Container Platform 4.21 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.21/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:7ca8870aa5e505f969aa26161594a3f99b65baf7d29bab8adaca0cade51b0bb6 (For s390x architecture) The image digest is sha256:b33dc753fbb59cc939496922a7f65b3eaf145214f5635c9824790a5bc7a0b5a2 (For ppc64le architecture) The image digest is sha256:46bd467d5cee3e80019ef25c8af7460dfee7e5ae376dd640b76251666eafc98a (For aarch64 architecture) The image digest is sha256:6d018f320d0ba0496fe3410470c2ea3c58e9d77a95fe0f64f3120bc1115f9bf1 All OpenShift Container Platform 4.21 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.21/html-single/updating_clusters/index#updating-cluster-cli.
    After
    < 3.18.5 · Fixed: 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.
    Red Hat Product Security ↗
  2. Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2025-55198 to remediation: access.redhat.com/CVE-2025-55198.
    Before
    remediation: access.redhat.com/CVE-2025-55198
    After
    remediation: access.redhat.com/CVE-2025-55198
    Red Hat Product Security ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    dvo/deployment-validation-rhel8-operator as a component of Deployment Validation Operator; mta/mta-cli-rhel9 as a component of Migration Toolkit for Applications 7; multicluster-engine/addon-manager-rhel8 as a component of Multicluster Engine for Kubernetes; multicluster-engine/addon-manager-rhel9 as a component of Multicluster Engine for Kubernetes; multicluster-engine/backplane-rhel8-operator as a component of Multicluster Engine for Kubernetes; multicluster-engine/backplane-rhel9-operator as a component of Multicluster Engine for Kubernetes; multicluster-engine/cluster-proxy-rhel8 as a component of Multicluster Engine for Kubernetes; multicluster-engine/cluster-proxy-rhel9 as a component of Multicluster Engine for Kubernetes; multicluster-engine/hypershift-addon-rhel8-operator as a component of Multicluster Engine for Kubernetes; multicluster-engine/hypershift-addon-rhel9-operator as a component of Multicluster Engine for Kubernetes; multicluster-engine/managed-serviceaccount-rhel8 as a component of Multicluster Engine for Kubernetes; multicluster-engine/managed-serviceaccount-rhel9 as a component of Multicluster Engine for Kubernetes; multicluster-engine/managedcluster-import-controller-rhel8 as a component of Multicluster Engine for Kubernetes; multicluster-engine/managedcluster-import-controller-rhel9 as a component of Multicluster Engine for Kubernetes; multicluster-engine/multicloud-manager-rhel8 as a component of Multicluster Engine for Kubernetes; multicluster-engine/multicloud-manager-rhel9 as a component of Multicluster Engine for Kubernetes; multicluster-engine/placement-rhel8 as a component of Multicluster Engine for Kubernetes; multicluster-engine/placement-rhel9 as a component of Multicluster Engine for Kubernetes; multicluster-engine/registration-operator-rhel8 as a component of Multicluster Engine for Kubernetes; multicluster-engine/registration-operator-rhel9 as a component of Multicluster Engine for Kubernetes; multicluster-engine/registration-rhel8 as a component of Multicluster Engine for Kubernetes; multicluster-engine/registration-rhel9 as a component of Multicluster Engine for Kubernetes; multicluster-engine/work-rhel8 as a component of Multicluster Engine for Kubernetes; multicluster-engine/work-rhel9 as a component of Multicluster Engine for Kubernetes; multicluster-globalhub/multicluster-globalhub-agent-rhel9 as a component of Multicluster Global Hub; multicluster-globalhub/multicluster-globalhub-manager-rhel9 as a component of Multicluster Global Hub; multicluster-globalhub/multicluster-globalhub-operator-bundle as a component of Multicluster Global Hub; multicluster-globalhub/multicluster-globalhub-rhel9-operator as a component of Multicluster Global Hub; openshift-service-mesh/istio-cni-rhel8 as a component of OpenShift Service Mesh 2; openshift-service-mesh/pilot-rhel8 as a component of OpenShift Service Mesh 2; and 67 more · Fixed: registry.redhat.io/openshift4/ose-console-rhel9@sha256:33afbf29add637cae8478b8e0ef6b3b465e4ee53b000467ec34fb1f3a04615af_amd64 as a component of Red Hat OpenShift Container Platform 4.21; registry.redhat.io/openshift4/ose-console-rhel9@sha256:8056eca30416b0b93270f6c92d0fdbe4f1cfbbd6258e27a746cc379a86b6b8cd_ppc64le as a component of Red Hat OpenShift Container Platform 4.21; registry.redhat.io/openshift4/ose-console-rhel9@sha256:a06dfb4e75cc6b0edd836cd59035095135503f35a7cbc710ed7b0e447fe256f4_arm64 as a component of Red Hat OpenShift Container Platform 4.21; registry.redhat.io/openshift4/ose-console-rhel9@sha256:a820784083ee32f544efc474c7ded798916d1f077ddb9c3f4461de48747f4c73_s390x as a component of Red Hat OpenShift Container Platform 4.21; registry.redhat.io/openshift4/ose-console-rhel9@sha256:9ed3615bd5a3d77b498c4bb885b7b5902ae701b9d254ea8345c3ae76f0d7a791_ppc64le as a component of Red Hat OpenShift Container Platform 4.2; registry.redhat.io/openshift4/ose-console-rhel9@sha256:b59bae9eae260d0e740d92260b3b27128c24be7fb99363cab1d38ab0daf7b299_arm64 as a component of Red Hat OpenShift Container Platform 4.2; registry.redhat.io/openshift4/ose-console-rhel9@sha256:b8a70037384238ad8eb737ba5e2800ec7abce087aa1b7058982c4ee959d9c5a3_s390x as a component of Red Hat OpenShift Container Platform 4.2; registry.redhat.io/openshift4/ose-console-rhel9@sha256:fc2c5362f70f7c9ae8633ffdd98b7a27b062eff2585aa9178fe867e526c9677b_amd64 as a component of Red Hat OpenShift Container Platform 4.2
    After
    dvo/deployment-validation-rhel8-operator as a component of Deployment Validation Operator; mta/mta-cli-rhel9 as a component of Migration Toolkit for Applications 7; multicluster-engine/addon-manager-rhel8 as a component of Multicluster Engine for Kubernetes; multicluster-engine/addon-manager-rhel9 as a component of Multicluster Engine for Kubernetes; multicluster-engine/backplane-rhel8-operator as a component of Multicluster Engine for Kubernetes; multicluster-engine/backplane-rhel9-operator as a component of Multicluster Engine for Kubernetes; multicluster-engine/cluster-proxy-rhel8 as a component of Multicluster Engine for Kubernetes; multicluster-engine/cluster-proxy-rhel9 as a component of Multicluster Engine for Kubernetes; multicluster-engine/hypershift-addon-rhel8-operator as a component of Multicluster Engine for Kubernetes; multicluster-engine/hypershift-addon-rhel9-operator as a component of Multicluster Engine for Kubernetes; multicluster-engine/managed-serviceaccount-rhel8 as a component of Multicluster Engine for Kubernetes; multicluster-engine/managed-serviceaccount-rhel9 as a component of Multicluster Engine for Kubernetes; multicluster-engine/managedcluster-import-controller-rhel8 as a component of Multicluster Engine for Kubernetes; multicluster-engine/managedcluster-import-controller-rhel9 as a component of Multicluster Engine for Kubernetes; multicluster-engine/multicloud-manager-rhel8 as a component of Multicluster Engine for Kubernetes; multicluster-engine/multicloud-manager-rhel9 as a component of Multicluster Engine for Kubernetes; multicluster-engine/placement-rhel8 as a component of Multicluster Engine for Kubernetes; multicluster-engine/placement-rhel9 as a component of Multicluster Engine for Kubernetes; multicluster-engine/registration-operator-rhel8 as a component of Multicluster Engine for Kubernetes; multicluster-engine/registration-operator-rhel9 as a component of Multicluster Engine for Kubernetes; multicluster-engine/registration-rhel8 as a component of Multicluster Engine for Kubernetes; multicluster-engine/registration-rhel9 as a component of Multicluster Engine for Kubernetes; multicluster-engine/work-rhel8 as a component of Multicluster Engine for Kubernetes; multicluster-engine/work-rhel9 as a component of Multicluster Engine for Kubernetes; multicluster-globalhub/multicluster-globalhub-agent-rhel9 as a component of Multicluster Global Hub; multicluster-globalhub/multicluster-globalhub-manager-rhel9 as a component of Multicluster Global Hub; multicluster-globalhub/multicluster-globalhub-operator-bundle as a component of Multicluster Global Hub; multicluster-globalhub/multicluster-globalhub-rhel9-operator as a component of Multicluster Global Hub; openshift-service-mesh/istio-cni-rhel8 as a component of OpenShift Service Mesh 2; openshift-service-mesh/pilot-rhel8 as a component of OpenShift Service Mesh 2; and 67 more · Fixed: registry.redhat.io/openshift4/ose-console-rhel9@sha256:9ed3615bd5a3d77b498c4bb885b7b5902ae701b9d254ea8345c3ae76f0d7a791_ppc64le as a component of Red Hat OpenShift Container Platform 4.20; registry.redhat.io/openshift4/ose-console-rhel9@sha256:b59bae9eae260d0e740d92260b3b27128c24be7fb99363cab1d38ab0daf7b299_arm64 as a component of Red Hat OpenShift Container Platform 4.20; registry.redhat.io/openshift4/ose-console-rhel9@sha256:b8a70037384238ad8eb737ba5e2800ec7abce087aa1b7058982c4ee959d9c5a3_s390x as a component of Red Hat OpenShift Container Platform 4.20; registry.redhat.io/openshift4/ose-console-rhel9@sha256:fc2c5362f70f7c9ae8633ffdd98b7a27b062eff2585aa9178fe867e526c9677b_amd64 as a component of Red Hat OpenShift Container Platform 4.20; registry.redhat.io/openshift4/ose-console-rhel9@sha256:33afbf29add637cae8478b8e0ef6b3b465e4ee53b000467ec34fb1f3a04615af_amd64 as a component of Red Hat OpenShift Container Platform 4.21; registry.redhat.io/openshift4/ose-console-rhel9@sha256:8056eca30416b0b93270f6c92d0fdbe4f1cfbbd6258e27a746cc379a86b6b8cd_ppc64le as a component of Red Hat OpenShift Container Platform 4.21; registry.redhat.io/openshift4/ose-console-rhel9@sha256:a06dfb4e75cc6b0edd836cd59035095135503f35a7cbc710ed7b0e447fe256f4_arm64 as a component of Red Hat OpenShift Container Platform 4.21; registry.redhat.io/openshift4/ose-console-rhel9@sha256:a820784083ee32f544efc474c7ded798916d1f077ddb9c3f4461de48747f4c73_s390x as a component of Red Hat OpenShift Container Platform 4.21
    Red Hat Product Security ↗
  4. Affected versionsThe structured affected or fixed version information changed.
    Before
    < 3.18.5 · Fixed: 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.
    After
    < 3.18.5 · Fixed: For OpenShift Container Platform 4.21 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.21/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:7ca8870aa5e505f969aa26161594a3f99b65baf7d29bab8adaca0cade51b0bb6 (For s390x architecture) The image digest is sha256:b33dc753fbb59cc939496922a7f65b3eaf145214f5635c9824790a5bc7a0b5a2 (For ppc64le architecture) The image digest is sha256:46bd467d5cee3e80019ef25c8af7460dfee7e5ae376dd640b76251666eafc98a (For aarch64 architecture) The image digest is sha256:6d018f320d0ba0496fe3410470c2ea3c58e9d77a95fe0f64f3120bc1115f9bf1 All OpenShift Container Platform 4.21 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.21/html-single/updating_clusters/index#updating-cluster-cli.
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
Fixed release recorded from official guidance
Fixed release recorded from official guidance
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2025-55198 · cve.blacktree.nl