# CVE-2026-86144: Server-side request forgery in libxml2

> Attackers can trigger SSRF or DoS via XInclude processing in libxml2 due to missing parse flag propagation, affecting applications using the library.

- **Severity:** Medium 5.6 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Sep 2026
- **Updated:** 8 Sep 2026
- **Also known as:** AZL-99702, BELL-CVE-2026-86144, DEBIAN-CVE-2026-86144, ECHO-0085-7842-c8d6, GHSA-h6w8-m27h-f268, ROOT-OS-DEBIAN-12-CVE-2026-86144, UBUNTU-CVE-2026-86144

## What is CVE-2026-86144?

CVE-2026-86144 is a medium-severity server-side request forgery vulnerability in Xmlsoft Libxml2, published on 5 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In xinclude in libxml2 before 2.15.4, xmlXIncludeProcess and xmlXIncludeProcessTree do not propagate parseFlags. This has security relevance for, for example, the XML_PARSE_NONET flag, if (without it) a custom resource loader accesses the internet and triggers XML external entity injection, SSRF, or a denial of service (e.g., for an attacker-controlled internet resource that is intentionally slow).

Weakness: CWE-669 (Incorrect Resource Transfer Between Spheres)

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

It affects 1 product.


Products: Xmlsoft Libxml2.

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

Upgrade to a fixed version.

## Is CVE-2026-86144 being exploited?

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

## Other vulnerabilities in Xmlsoft Libxml2

- [CVE-2017-16931](https://insights.sbomify.com/CVE-2017-16931/): XML external entity in n/a (critical 9.8)
- [CVE-2017-8872](https://insights.sbomify.com/CVE-2017-8872/): Information disclosure in n/a (critical 9.1)
- [CVE-2022-49043](https://insights.sbomify.com/CVE-2022-49043/): Use after free in libxml2 (high 8.1)
- [CVE-2026-86140](https://insights.sbomify.com/CVE-2026-86140/): Memory corruption in libxml2 (high 8.0)
- [CVE-2024-34459](https://insights.sbomify.com/CVE-2024-34459/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-86144 is a medium-severity server-side request forgery vulnerability in Xmlsoft Libxml2, published on 5 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-86144 in the wild and no public exploit code.

Affected product: Xmlsoft Libxml2. 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-86144/ (Markdown: https://insights.sbomify.com/CVE-2026-86144/index.md)
```

## Sources

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

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