CVE-2024-56171VulnerabilityPublished 26 Mar 2025Updated 25 Oct 2026

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

Affects Red HatSource GCVE Database

Mentioned vulnerabilities

CVE-2025-27144

Authoritative record:CVE-2024-56171· High 7.8

Not known to be exploited · CVSS 7.8 High · fixed in 4.17.22 : patch Red Hat soon.

Data as of 26 Oct 2026, 06:26 UTC

CVSS base score

7.8High

How severe the flaw is on the 0–10 CVSS scale.

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

Exploitation evidence

Disclosed: evidence found.
CVE published 18 Feb 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-26.

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

Affected software

Product	Affected	Fixed in
Debiandebian/libxml2`pkg:deb/debian/libxml2`Other threats	Affected =0 =2.13.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Red Hat has released OpenShift Container Platform 4.17.22 containing fixes for these vulnerabilities. Users should upgrade to version 4.17.22 using the OpenShift CLI (oc) or web console when the updated packages and container images become available in their release channel. Detailed upgrade instructions are available at Red Hat's official documentation. Since this is an official fix, applying the update fully mitigates the vulnerabilities.

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.17.22. See the following advisory for the RPM packages for this release: https://access.redhat.com/errata/RHSA-2025:3061 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.17/html/release_notes/ Security Fix(es): * libxml2: Use-After-Free in libxml2 (CVE-2024-56171) * go-jose: Go JOSE's Parsing Vulnerable to Denial of Service (CVE-2025-27144) 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.17/html-single/updating_clusters/index#updating-cluster-cli.

Impact

The vulnerabilities fixed in this update include a Use-After-Free in libxml2, which can lead to memory corruption, and a denial of service vulnerability in Go JOSE's parsing. These issues could cause application crashes or denial of service conditions within the OpenShift Container Platform environment. No active exploitation in the wild has been reported. The overall security impact is rated as important by Red Hat.

Summary

This advisory covers security fixes in Red Hat OpenShift Container Platform 4.17.22, specifically addressing two vulnerabilities: CVE-2024-56171, a Use-After-Free vulnerability in libxml2, and CVE-2025-27144, a denial of service vulnerability in Go JOSE's parsing. These vulnerabilities could potentially be exploited to cause application instability or denial of service conditions. The update includes container image and RPM package fixes. Red Hat recommends all OpenShift Container Platform 4.17 users upgrade to 4.17.22 to apply these fixes. Detailed upgrade instructions and image digests are provided by Red Hat. The advisory does not include a CVSS score but rates the impact as important.

CWE-416Use After Free (opens in a new tab)
Variant weaknessLikelihood of exploit: HighCWE Top 25 (2025): #7
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
Architecture and Design · Language Selection
Choose a language that provides automatic memory management.
Implementation · Attack Surface Reduction
When freeing pointers, be sure to set them to NULL once they are freed. However, the utilization of multiple or complex data structures may lower the usefulness of this strategy.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
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 10 Aug 2026, 18:20 UTC

WeaknessesCWE-416, CWE-770

Technical details

References

Community reviews

Related threats