CVE-2025-55198VulnerabilityPublished 2 Dec 2025Updated 8 Sep 2026

Red Hat Security Advisory: OpenShift Container Platform 4.20.6 bug fix and security update

Affects Red HatSource GCVE Database

Mentioned vulnerabilities

CVE-2025-55199

Not known to be exploited : upgrade to 4.20.6 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

Severity

Medium

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 4.20.6

Exploitation evidence

Disclosed: evidence found.
CVE published 2 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Red Hat to 4.20.6.

Affected software

Product	Affected	Fixed in
Red Hat Product Security Red Hat	Affected >=4.20.0 <4.20.6 Red Hat Red Hat OpenShift Container Platform Red Hat OpenShift Container Platform 4.2 amd64 registry.redhat.io/openshift4/ose-agent-installer-ui-rhel9@sha256:de64ad2e8aa5d9d2c8884e1eb50c3dc7983c00d53d7dd4fa9a3777f649ba167f_amd64 ppc64le registry.redhat.io/openshift4/volume-data-source-validator-rhel9@sha256:f4d9e648e0de548f9bb02e08d869a8df1e7303d349d798c796548c976186e8ae_ppc64le	Fixed in 4.20.6

AI-suggested

Red Hat has released OpenShift Container Platform 4.20.6 which includes fixes for this vulnerability. Users should upgrade to version 4.20.6 or later using the OpenShift CLI or web console as per Red Hat's official upgrade instructions. Additionally, ensuring that YAML files are properly formatted before processing with Helm can mitigate the risk. No other mitigations are specified by the vendor.

Description

Red Hat OpenShift Container Platform is Red Hat's cloud computing Kubernetes application platform solution designed for on-premise or private cloud deployments. This advisory contains the container images for Red Hat OpenShift Container Platform 4.20.6. See the following advisory for the RPM packages for this release: https://access.redhat.com/errata/156635 Space precludes documenting all of the container images in this advisory. See the following Release Notes documentation, which will be updated shortly for this release, for details about these changes: https://docs.redhat.com/en/documentation/openshift_container_platform/4.20/html/release_notes/ Security Fix(es): * helm.sh/helm/v3: Helm Chart JSON Schema Denial of Service (CVE-2025-55199) * helm.sh/helm/v3: Helm YAML Parsing Panic Vulnerability (CVE-2025-55198) For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section. 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.

Impact

Successful exploitation can cause a denial of service by triggering a panic in Helm's YAML parsing component, potentially disrupting application deployment or management within OpenShift clusters. There is no impact on confidentiality or integrity. The vulnerability requires user interaction and network access to deliver a malformed chart file.

Summary

A vulnerability (CVE-2025-55198) was found in helm.sh/helm/v3 used by Red Hat OpenShift Container Platform. It involves improper validation of type errors during parsing of Chart.yaml and index.yaml files, which can trigger a panic and cause an application-level denial of service. Exploitation requires user interaction with a malformed chart file. The vulnerability is addressed in OpenShift Container Platform 4.20.6 through updated container images and packages. Red Hat rates the security impact as moderate with a CVSS base score of 6.5 (availability impact high, no confidentiality or integrity impact).

CWE-908Use of Uninitialized Resource (opens in a new tab)
Base weaknessLikelihood of exploit: Medium
The product uses or accesses a resource that has not been initialized.
Implementation
Explicitly initialize the resource before use. If this is performed through an API function or standard procedure, follow all required steps.
Implementation
Pay close attention to complex conditionals that affect initialization, since some branches might not perform the initialization.
Implementation
Avoid race conditions (CWE-362) during initialization routines.
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-770Allocation of Resources Without Limits or Throttling (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #25
The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.
Requirements
Clearly specify the minimum and maximum expectations for capabilities, and dictate which behaviors are acceptable when resource allocation reaches limits.
Architecture and Design
Limit the amount of resources that are accessible to unprivileged users. Set per-user limits for resources. Allow the system administrator to define these limits. Be careful to avoid CWE-410.
Architecture and Design
Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
OWASP ASVS 4.0.3
V8.1.4 (opens in a new tab)
V13.4.1 (opens in a new tab)
V11.1.4 (opens in a new tab)
Attack patterns
XML Ping of the Death (opens in a new tab)
Exponential Data Expansion (opens in a new tab)
Serialized Data Parameter Blowup (opens in a new tab)
Serialized Data with Nested Payloads (opens in a new tab)
Oversized Serialized Data Payloads (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 16 Aug 2026, 17:19 UTC

WeaknessesCWE-908, CWE-770

Technical details

References

Community reviews

Related threats