CVE-2025-6021: Libxml2: integer overflow in xmlbuildqname() leads to stack buffer overflow in libxml2
A flaw was found in libxml2's xmlBuildQName function, where integer overflows in buffer size calculations can lead to a stack-based buffer overflow. This issue can result in memory corruption or a denial of service when processing crafted input.
Security readout for executives and security teams
Plain-English summary
CVE-2025-6021 is a high-severity libxml2 flaw that can crash software when crafted XML-related input triggers a stack buffer overflow. The direct business risk is availability loss in systems that process untrusted XML using affected Red Hat packages.
Executive priority
Treat as a high-priority availability risk for internet-facing or partner-facing XML-processing systems. It is not currently supported as known exploited in the provided evidence, but patching should be scheduled promptly because exploitation requires no authentication or user interaction.
Technical view
The flaw is in libxml2 xmlBuildQName(). Integer overflow during buffer-size calculation can lead to stack-based buffer overflow, memory corruption, or denial of service. The CVSS 3.1 vector is network exploitable with low complexity, no privileges, and no user interaction, but the listed impact is availability only.
Likely exposure
Exposure is most likely on Red Hat Enterprise Linux 7 ELS, 8, 9, 10, supported update streams, and OpenShift Container Platform 4.12 rhcos where vulnerable libxml2 packages are installed and parse untrusted input.
Exploitation context
The bundle marks KEV as false and provides no cited evidence of active exploitation. The CVSS vector indicates remote, unauthenticated triggering may be possible in applications that expose XML parsing paths to attacker-controlled input.
Researcher notes
Focus validation on reachable code paths into libxml2 xmlBuildQName(), especially QName construction from attacker-controlled XML content. The public bundle supports denial-of-service and memory-corruption impact, but does not establish confidentiality, integrity impact, exploit availability, or active exploitation.
Mitigation direction
Apply applicable Red Hat RHSA updates for affected RHEL and OpenShift products.
Prioritize externally reachable services that parse XML or XML-derived formats.
Reduce or block untrusted XML processing where patching is delayed.
Check non-Red Hat libxml2 deployments against their vendor advisories.
Track Red Hat errata for fixed package availability in each stream.
Validation and detection
Inventory libxml2 package versions across Linux hosts and container bases.
Map installed versions to the affected Red Hat versions in the CVE bundle.
Identify applications accepting XML or namespace-qualified input from networks or users.
Confirm RHSA updates are installed in RHEL and OpenShift images.
Monitor exposed XML-processing services for crashes or abnormal restarts.
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-787: 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-787 · source CWE mapping
Out-of-bounds Write
Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.