CVE-2026-0992: Libxml2: libxml2: denial of service via crafted xml catalogs
A flaw was found in the libxml2 library. This uncontrolled resource consumption vulnerability occurs when processing XML catalogs that contain repeated <nextCatalog> elements pointing to the same downstream catalog. A remote attacker can exploit this by supplying crafted catalogs, causing the parser to redundantly traverse catalog chains. This leads to excessive CPU consumption and degrades application availability, resulting in a denial-of-service condition.
Security readout for executives and security teams
Plain-English summary
CVE-2026-0992 can make applications using libxml2 consume excessive CPU when they process a specially crafted XML catalog. The result is degraded availability or denial of service, not data theft or modification. Red Hat rates the issue low severity, with a CVSS 3.1 score of 2.9.
Executive priority
Handle through routine vulnerability management, prioritizing exposed or availability-sensitive XML-processing services. Escalate if untrusted catalog input is reachable or CPU exhaustion would disrupt critical operations. The supplied evidence does not support emergency incident response.
Technical view
Repeated <nextCatalog> elements referencing the same downstream catalog can cause redundant catalog-chain traversal and uncontrolled CPU consumption (CWE-400). The supplied affected list includes libxml2 packages across several Red Hat products. The CVSS vector indicates local access, high attack complexity, no privileges or user interaction, and low availability impact.
Likely exposure
Exposure is most likely where affected Red Hat systems or containers use libxml2 to process attacker-influenced XML catalogs. Listed products include RHEL 6–10, Hardened Images, JBoss Core Services, and OpenShift Container Platform 4 components. Exact affected version ranges are incomplete in the bundle.
Exploitation context
The bundle does not establish active exploitation, and the CVE is not listed as KEV. Although the description calls the attacker remote, the supplied CVSS vector is AV:L. Treat practical reachability as application-dependent and verify whether untrusted catalogs can reach libxml2 processing.
Researcher notes
Key uncertainties are the remote-attacker wording versus the AV:L vector, missing version ranges for most products, and absent fix details in the bundle. Validate attack preconditions and corrected builds against current vendor advisories. Do not infer broader libxml2 product exposure beyond the supplied affected list.
Mitigation direction
Review Red Hat's CVE page and RHSA-2026:7519 for applicable package updates.
Apply vendor-provided updates according to normal change-control procedures.
Restrict processing of untrusted XML catalogs where operationally feasible.
Monitor affected services for abnormal CPU consumption and availability degradation.
Validation and detection
Inventory libxml2 and libxml2-main packages across listed Red Hat products.
Compare installed package versions with Red Hat's current advisory status.
Trace whether applications accept attacker-controlled XML catalogs or catalog references.
Confirm CPU monitoring and service-recovery controls cover XML-processing workloads.
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-400: 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-400 · source CWE mapping
Uncontrolled Resource Consumption
Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.