CVE-2026-0989LowMicrosoft CVSS 3.7CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L

Microsoft security update for CVE-2026-0989

Published
June 2, 2026
Last Modified
—

🔗 CVE IDs covered (1)

📋 Microsoft's advisory

EchelonGraph does not copy Microsoft's advisory page: its FAQ and remediation text are not shown here. Read the advisory on https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-0989. This page also shows what EchelonGraph holds for CVE-2026-0989, with the description from its CVE record, which the CVE Numbering Authority that assigned the CVE wrote: for a CVE Microsoft assigned, often in the words of Microsoft's own advisory.

🎯 Affected products9

  • azl3 libxml2 2.11.5-10 on Azure Linux 3.0
  • azl3 libxml2 2.11.5-7 on Azure Linux 3.0
  • azl3 libxml2 2.11.5-8 on Azure Linux 3.0
  • azl3 libxml2 2.11.5-9 on Azure Linux 3.0
  • cbl2 libxml2 2.10.4-10 on CBL Mariner 2.0
  • cbl2 libxml2 2.10.4-11
  • cbl2 libxml2 2.10.4-11 on CBL Mariner 2.0
  • cbl2 libxml2 2.10.4-11 on CBL-Mariner 2.0
  • cbl2 libxml2 2.10.4-9 on CBL Mariner 2.0

✅ Updates Microsoft lists: 2 updates

2 rows: one per KB article or update, update type and fixed build. Their details are on Microsoft's advisory.

KB articleUpdateFixed build
—Security Update2.11.5-10
—Security Update—

🧭 EchelonGraph on CVE-2026-0989

EchelonGraph score
3.7 LOW
CISA KEV
Not listed
Fix status
A fix is available — apply it.

Description from the CVE record (CVE.org), as published by its numbering authority

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 by Red Hat, Inc., the CVE Numbering Authority that assigned CVE-2026-0989, in its CVE record at CVE.org; reused under the CVE Program's Terms of Use (its licence and MITRE's copyright notice are in our Terms of Service).

🔗 References (2)