CVE-2025-49794: Libxml: heap use after free (uaf) leads to denial of service (dos)
A use-after-free vulnerability was found in libxml2. This issue occurs when parsing XPath elements under certain circumstances when the XML schematron has the <sch:name path="..."/> schema elements. This flaw allows a malicious actor to craft a malicious XML document used as input for libxml, resulting in the program's crash using libxml or other possible undefined behaviors.
Security readout for executives and security teams
Plain-English summary
CVE-2025-49794 is a libxml2 memory-safety flaw. A crafted XML document can crash software that uses libxml2 under specific Schematron/XPath parsing conditions. Because libxml2 is a common system library, exposure may be indirect through applications and platforms, not just visibly installed tools.
Executive priority
Treat as urgent for Linux platform and application owners, especially where XML is accepted from outside trusted systems. The main documented business impact is service disruption, but the critical rating and common library footprint justify expedited remediation planning.
Technical view
The issue is a heap use-after-free during XPath element parsing when XML Schematron includes sch:name elements with path attributes. Red Hat rates it critical with CVSS 3.1 score 9.1. Public text emphasizes denial of service and undefined behavior; it does not confirm code execution.
Likely exposure
Organizations using affected Red Hat libxml2 packages on RHEL 7 ELS, 8, 9, 10 variants, or affected OpenShift Container Platform 4.12 RHCOS should assess exposure. Risk is highest where services parse untrusted XML content or XML supplied by users, partners, or automated feeds.
Exploitation context
The CVE record is not marked KEV, and the provided sources do not show active exploitation. The CVSS vector indicates network attackability, low complexity, no privileges, and no user interaction. Real-world exploitability depends on applications exposing libxml2 XML parsing to attacker-controlled input.
Researcher notes
Focus validation on dependency reachability, not just package presence. The trigger involves Schematron sch:name path handling during XPath parsing. Sources provide affected Red Hat package streams and advisories, but not detailed exploit evidence. Avoid assuming exploitation in products unless the application actually processes attacker-controlled XML through libxml2.
Mitigation direction
Apply the relevant Red Hat security advisory updates for affected RHEL and OpenShift deployments.
Update libxml2 packages through supported vendor channels where applicable.
For OpenShift, follow Red Hat guidance for affected RHCOS/OCP updates.
Prioritize internet-facing or partner-facing systems that parse XML input.
If patch timing is delayed, reduce acceptance of untrusted XML where operationally feasible.
Validation and detection
Inventory installed libxml2 packages and compare against Red Hat affected package versions.
Check Red Hat errata applicability for each RHEL, EUS, AUS, E4S, TUS, or ELS channel.
Identify applications and containers that parse XML using system libxml2.
Confirm OpenShift 4.12 clusters are not running affected RHCOS builds.
Monitor XML-processing services for crashes or abnormal parser failures.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-825: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-825 · source CWE mapping
Expired Pointer Dereference
Expired Pointer Dereference represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.