CVE-2024-25062VulnerabilityPublished 2 May 2024Updated 11 Oct 2026

SUSE · security update for libxml2

Affects SUSESource GCVE Database

Not known to be exploited.

Data as of 25 Oct 2026, 19:02 UTC

Severity

Medium

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

EPSS: 1.3% chance of exploitation in 30 days – higher than 70% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

Exploitation evidence

Disclosed: evidence found.
CVE published 2 May 2024
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

Affected software

Product	Affected	Fixed in
Red Hatredhat/libxml2`pkg:rpm/redhat/libxml2`Other threats	Affected =8.0.0 <=8.10	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 official security updates addressing this vulnerability. Users should apply the provided libxml2 updates for their respective Red Hat Enterprise Linux 8 or 9 versions. After applying the update, a desktop session restart (log out and log back in) is required for the fix to take effect. No additional mitigation steps are indicated by the vendor.

Description

A use-after-free vulnerability (CWE-416) exists in the XMLReader component of the libxml2 library, tracked as CVE-2024-25062. This vulnerability affects multiple versions of Red Hat Enterprise Linux 8 and 9 across various architectures. Exploitation could lead to memory corruption or application crashes. Red Hat has released security updates to address this issue and recommends applying these updates and restarting the desktop session for the fix to take effect. The severity is rated as moderate.

Impact

Successful exploitation of this use-after-free vulnerability could result in memory corruption or application crashes, potentially affecting system stability or security. However, no known exploits are reported in the wild at this time. The impact is rated as moderate by Red Hat.

Summary

CVE-2024-25062 is a use-after-free vulnerability in the XMLReader component of the libxml2 library. This flaw can cause memory corruption or crashes when processing XML data. It affects multiple versions of Red Hat Enterprise Linux 8 and 9 on various hardware architectures including x86_64, s390x, ppc64le, and aarch64. Red Hat has issued security advisories and updates to remediate this vulnerability. The fix requires updating the libxml2 package and restarting the desktop session to fully apply the patch.

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

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Oct 2026, 22:36 UTC

WeaknessesCWE-416

Technical details

References

Community reviews

Related threats