CVE-2025-0624VulnerabilityPublished 17 Apr 2025Updated 13 Oct 2026

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

Affects Red HatSource GCVE Database

Mentioned vulnerabilities

CVE-2025-24928

Not known to be exploited : upgrade Red Hat to 4.13.57 soon.

Data as of 26 Oct 2026, 08:30 UTC

Severity

High

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

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

Exploitation evidence

Disclosed: evidence found.
CVE published 17 Apr 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 26 Oct 2026.

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.13.57.

Affected software

Product	Affected	Fixed in
Red Hat Product Security Red Hat	Affected >=4.13.0 <4.13.57 Red Hat Red Hat OpenShift Enterprise Red Hat OpenShift Container Platform 4.13 amd64 Red Hat Enterprise Linux Red Hat Enterprise Linux BaseOS EUS (v.8.8) src grub2-1:2.02-152.el8_8.2.src 0 SUSE noarch grub2-common-1:2.06-94.el9_5.noarch grub2-efi-x64-modules-1:2.06-94.el9_5.noarch grub2-pc-modules-1:2.06-94.el9_5.noarch	Fixed in 4.13.57

AI-suggested

A fix is available in Red Hat OpenShift Container Platform version 4.13.57. Users should upgrade to this version using the OpenShift CLI (oc) or web console as soon as the update is available in their release channel. Detailed upgrade instructions are provided by Red Hat at https://docs.redhat.com/en/documentation/openshift_container_platform/4.13/html-single/updating_clusters/index#updating-cluster-within-minor. No additional mitigation steps are indicated by the vendor advisory.

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.13.57. 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.13/html/release_notes Security Fix(es): * grub2: net: Out-of-bounds write in grub_net_search_config_file() (CVE-2025-0624) * libxml2: Stack-based buffer overflow in xmlSnprintfElements of libxml2 (CVE-2025-24928) 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.13/html-single/updating_clusters/index#updating-cluster-within-minor.

Impact

The vulnerabilities fixed in this update include an out-of-bounds write and a stack-based buffer overflow, which could lead to memory corruption. Such issues may affect the stability and security of the OpenShift Container Platform environment. The advisory rates the security impact as important (high severity). No known exploits in the wild have been reported at the time of this advisory.

Summary

This advisory covers security updates in Red Hat OpenShift Container Platform 4.13.57 that fix two vulnerabilities: CVE-2025-0624, an out-of-bounds write in grub2's grub_net_search_config_file() function, and CVE-2025-24928, a stack-based buffer overflow in libxml2's xmlSnprintfElements function. Both vulnerabilities could potentially lead to memory corruption issues. The advisory recommends upgrading to OpenShift Container Platform 4.13.57, which contains updated container images and packages addressing these security flaws. The update is rated as having an important security impact by Red Hat Product Security.

CWE-787Out-of-bounds Write (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #5
The product writes data past the end, or before the beginning, of the intended buffer.
Requirements · Language Selection
Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Operation · Build and Compilation · Environment Hardening
Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index…
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-121Stack-based Buffer Overflow (opens in a new tab)
Variant weaknessLikelihood of exploit: HighCWE Top 25 (2025): #14
A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function).
Operation · Build and Compilation · Environment Hardening
Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index…
Architecture and Design
Use an abstraction library to abstract away risky APIs. Not a complete solution.
Implementation
Implement and perform bounds checking on input.
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).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 17 Aug 2026, 21:56 UTC

WeaknessesCWE-787, CWE-121

Technical details

References

Community reviews

Related threats