CVE-2026-56412: Use After Free

Published Jun 21, 2026
·
Updated

libexpat before 2.8.2 does not consider XMLTOKDATACHARS 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.

Affected Software

3 affected componentsFixes available
Expat libexpat<2.8.2
Libexpat Project Libexpat<2.8.2
Microsoft azl3 expat 2.6.4-6<2.8.2-1
2.8.2-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.8.2-1
  2. Upgrade

    Upgrade libexpat to a version that resolves this vulnerability.

    Fixed in 2.8.2
  3. Compensating control

    If you cannot upgrade past libexpat versions before 2.8.2 immediately, mitigate exploitation by limiting/isolating exposure of XML parsing workflows that could trigger policy-violation handling paths (e.g., restrict who can supply XML and isolate the parsing service).

Event History

Jun 21, 2026
CVE Published
via MITRE·03:58 PM
Data Sourced
via MITRE·03:58 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Jun 27, 2026
Data Sourced
via Microsoft·08:07 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·08:07 AM
DescriptionSeverity
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-56412?

The severity of CVE-2026-56412 is medium with a score of 4.9.

2

How does CVE-2026-56412 impact libexpat?

CVE-2026-56412 can lead to a use-after-free vulnerability due to lack of handler call depth tracking.

3

What versions of libexpat are affected by CVE-2026-56412?

libexpat versions before 2.8.2 are affected by CVE-2026-56412.

4

How can I mitigate CVE-2026-56412?

The recommended mitigation for CVE-2026-56412 is to update libexpat to version 2.8.2 or later.

5

Is CVE-2026-56412 related to any previous vulnerabilities?

Yes, CVE-2026-56412 is connected to an incomplete fix for CVE-2026-50219.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203