CVE-2026-0989 | Libxml2: unbounded relaxng include recursion leading to stack overflow

A flaw was identified in the RelaxNG parser of libxml2 related to how external schema inclusions are handled. The parser does not enforce a limit on inclusion depth when resolving nested <include> directives. Specially crafted or overly complex schemas can cause excessive recursion during parsing. This may lead to stack exhaustion and application crashes, creating a denial-of-service risk.

Published: 2026-01-15 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-0989 is rated Low Risk (25.9/100): CVSS Low severity, with low exploitation likelihood (EPSS 0.39%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-0989

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.02% 0.39% +0.37%
2 2026-02-18 0.06% 0.02% -0.04%
3 2026-01-21 — 0.06% —

Full EPSS history (4 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-0989

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
3.7 3.1 LOW
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
 2.2 1.4 [email protected]

Weakness enumeration for CVE-2026-0989

GitHub Security Advisory for CVE-2026-0989

GHSA-3xfm-x84x-qwwq · Severity: low — A flaw was identified in the RelaxNG parser of libxml2 related to how external schema inclusions...

OS Trackers for CVE-2026-0989

vendor priority summary link
debian not yet assigned CVE-2026-0989 not yet assigned priority: Debian including 1 source packages (libxml2), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 3, open 2. https://security-tracker.debian.org/tracker/CVE-2026-0989
redhat low — https://access.redhat.com/security/cve/CVE-2026-0989
suse medium CVE-2026-0989 severity moderate: SUSE including 319 source package names (1.1.1-1.29:libxml2-2-2.12.10-150700.4.11.1, 13.2-9.72:findutils-4.9.0-4.1, …), 661 product×package rows across 174 product lines (Container private-registry/harbor-portal, Container suse/ltss/sle12.5/sles12sp5, … (174 product lines)): Fixed 425, Known Affected 231, First Fixed 5. https://www.suse.com/security/cve/CVE-2026-0989/
ubuntu medium CVE-2026-0989 medium priority: Ubuntu including 1 source packages (libxml2), 8 status rows across 8 suites (bionic, focal, jammy, noble, questing, trusty, upstream, xenial): released 7, needs-triage 1. https://ubuntu.com/security/CVE-2026-0989

Affected software / configurations for CVE-2026-0989

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2026-0989

cvelogic Threat Intelligence