Affected versions
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
Exploitation
Description
libexpat before 2.8.2 lacks handler call depth tracking for calls to XML_ResumeParser from within handlers in cases of a policy violation. Thus, a use-after-free can occur (similar to the CVE-2026-50219 situation).
A use-after-free vulnerability in libexpat occurs because handler call depth isn't properly tracked when XML_ResumeParser is invoked during policy violations. This flaw can lead to information disclosure, data corruption, or denial of service.

