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

> Attackers can cause application crashes via stack overflow by exploiting unbounded recursion in libxml2's RelaxNG parser when processing crafted schemas.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Jan 2026
- **Updated:** 1 Sep 2026
- **Also known as:** AZL-74775, AZL-74786, BELL-CVE-2026-0989, DEBIAN-CVE-2026-0989, ECHO-8419-807a-4b8d, GHSA-3xfm-x84x-qwwq, JLSEC-2026-1237, SUSE-SU-2026:0334-1, SUSE-SU-2026:0336-1, SUSE-SU-2026:0391-1, SUSE-SU-2026:20233-1, SUSE-SU-2026:20234-1, SUSE-SU-2026:20353-1, SUSE-SU-2026:20372-1, UBUNTU-CVE-2026-0989, openSUSE-SU-2026:10085-1, openSUSE-SU-2026:20178-1

## What is CVE-2026-0989?

CVE-2026-0989 is a low-severity denial of service vulnerability in Ibm Aix, published on 15 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-674 (Uncontrolled Recursion)

## Which versions are affected by CVE-2026-0989?

It affects 7 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libxml2` | SUSE:Linux Enterprise Micro 5.2 | All versions | 2.9.7-150000.3.91.1 |
| `python-libxml2-python` | SUSE:Linux Enterprise Micro 5.2 | All versions | 2.9.7-150000.3.91.1 |
| `libxml2` | SUSE:Linux Enterprise Micro 5.5 | All versions | 2.10.3-150500.5.35.1 |
| `libxml2-python` | SUSE:Linux Enterprise Micro 5.5 | All versions | 2.10.3-150500.5.35.1 |
| `libxml2` | SUSE:Linux Enterprise Server 16.0 | All versions | 2.13.8-160000.3.1 |
| `libxml2-python` | SUSE:Linux Enterprise Server 16.0 | All versions | 2.13.8-160000.3.1 |
| `libxml2` | SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | All versions | 2.9.4-46.96.1 |
| `python-libxml2` | SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | All versions | 2.9.4-46.96.1 |
| `libxml2` | SUSE:Linux Enterprise Server for SAP applications 16.0 | All versions | 2.13.8-160000.3.1 |
| `libxml2-python` | SUSE:Linux Enterprise Server for SAP applications 16.0 | All versions | 2.13.8-160000.3.1 |
| `libxml2` | SUSE:Linux Micro 6.0 | All versions | 2.11.6-11.1 |
| `libxml2` | SUSE:Linux Micro 6.1 | All versions | 2.11.6-slfo.1.1_7.1 |
| `libxml2` | SUSE:Linux Micro 6.2 | All versions | 2.13.8-160000.3.1 |
| `libxml2-python` | SUSE:Linux Micro 6.2 | All versions | 2.13.8-160000.3.1 |
| `libxml2` | openSUSE:Leap 15.6 | All versions | 2.10.3-150500.5.35.1 |
| `libxml2-python` | openSUSE:Leap 15.6 | All versions | 2.10.3-150500.5.35.1 |
| `python-libxml2-python` | openSUSE:Leap 15.6 | All versions | 2.9.7-150000.3.91.1 |
| `libxml2` | openSUSE:Leap 16.0 | All versions | 2.13.8-160000.3.1 |
| `libxml2-python` | openSUSE:Leap 16.0 | All versions | 2.13.8-160000.3.1 |
| `libxml2` | openSUSE:Tumbleweed | All versions | 2.14.5-2.1 |

Products: Ibm Aix, Ibm Vios, Redhat Enterprise Linux, Redhat Hardened Images, Redhat Jboss Core Services, Redhat Openshift Container Platform, Xmlsoft Libxml2.

## How do I fix CVE-2026-0989?

Apply the vendor's patch.

## Is CVE-2026-0989 being exploited?

There is no known exploitation of CVE-2026-0989 in the wild and no public exploit code.

## Other vulnerabilities in Ibm Aix

- [CVE-2025-36250](https://insights.sbomify.com/CVE-2025-36250/): AIX Code Execution (critical 10.0)
- [CVE-2024-56346](https://insights.sbomify.com/CVE-2024-56346/): IBM AIX command execution (critical 10.0)
- [CVE-2010-3187](https://insights.sbomify.com/CVE-2010-3187/): Memory corruption in n/a (critical 10.0)
- [CVE-2009-3699](https://insights.sbomify.com/CVE-2009-3699/): Memory corruption in n/a (critical 10.0)
- [CVE-2009-3517](https://insights.sbomify.com/CVE-2009-3517/): Auth bypass in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-0989 and fix it if it is affected.

What it is: CVE-2026-0989 is a low-severity denial of service vulnerability in Ibm Aix, published on 15 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-0989 in the wild and no public exploit code.

Affected product: Ibm Aix. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-0989/ (Markdown: https://insights.sbomify.com/CVE-2026-0989/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-0989
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-0989
- OSV: https://osv.dev/vulnerability/CVE-2026-0989

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-0989/
Summaries are generated and may contain mistakes; the official description above is the record.
