Security readout for executives and security teams
Plain-English summary
Libxml2 can crash when processing a RelaxNG schema containing deeply nested external inclusions. The resulting stack exhaustion creates a denial-of-service condition, not a disclosed confidentiality or integrity impact. Business risk is generally low, but services processing attacker-controlled schemas could experience availability disruption.
Executive priority
Treat as a low-priority maintenance vulnerability overall. Accelerate assessment for externally reachable services that parse untrusted RelaxNG schemas, because a successful trigger could interrupt availability. Apply vendor-supported remediation through normal change control and confirm exposed parsing paths are constrained.
Technical view
The RelaxNG parser lacks an inclusion-depth limit while resolving nested external <include> directives. Excessive recursion can exhaust the process stack and terminate the application. The issue is classified as CWE-674 and scored CVSS 3.1 at 3.7: network-reachable, high complexity, no privileges or user interaction, with availability impact only.
Likely exposure
Exposure is most likely where affected Red Hat systems, containers, or applications use libxml2 to parse RelaxNG schemas with external inclusions, particularly from untrusted sources. Listed products include RHEL 6–10, OpenShift 4 components, JBoss Core Services, and Red Hat Hardened Images. Exact affected versions are incomplete for most entries.
Exploitation context
The bundle does not identify public exploitation or inclusion in CISA KEV. Exploitation requires inducing an affected parser to process a sufficiently deep inclusion chain, which aligns with the high-complexity rating. The documented consequence is application crash and service interruption; no code execution, data disclosure, or modification is stated.
Researcher notes
The supplied record supports an unbounded-recursion root cause and stack-overflow outcome in RelaxNG external inclusion handling. Product scope is Red Hat-focused, and version boundaries are absent for most entries; do not infer broader package ranges from this bundle. The cited upstream issue may provide additional implementation context, but none is included here.
Mitigation direction
- Review RHSA-2026:7519 and product-specific Red Hat guidance for corrected packages or supported remediation.
- Prioritize systems that process untrusted or externally supplied RelaxNG schemas.
- Restrict untrusted schema ingestion and external schema resolution where operationally feasible.
- Use service supervision and resource isolation to reduce the impact of parser crashes.
Validation and detection
- Inventory affected Red Hat products and installed libxml2-related package versions.
- Identify applications and workflows that parse RelaxNG schemas or resolve external inclusions.
- Confirm whether schema inputs can originate from unauthenticated or untrusted network clients.
- Verify vendor remediation status against RHSA-2026:7519 before closing findings.
- Monitor relevant services for stack-exhaustion crashes or abnormal termination during XML schema processing.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-674: 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.
Open ATT&CK lookupContainer behavior lookup
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.
Open ATT&CK lookupCVE-2026-0989 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Low
- CVSS
- 3.7 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
CNA and ADP enrichment extracted from CVE v5
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L2.21.4redhatVulnerability scoring details
Base CVSS 3.1 score
3.7LowVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- Source timelineredhat
Made public.
- Source timelineredhat
Reported to Red Hat.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- RHSA-2026:7519CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/security/cve/CVE-2026-0989CVE reference, redhat · vdb-entry, x_refsource_REDHAT
- RHBZ#2429933CVE reference, redhat · issue-tracking, x_refsource_REDHAT
- https://gitlab.gnome.org/GNOME/libxml2/-/issues/998CVE reference, redhat
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Uncontrolled Recursion
Uncontrolled Recursion represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.