libxml2 through 2.11.5 has a use-after-free that can only occur after a certain memory allocation fails. This occurs in xmlUnlinkNode in tree.c. NOTE: the vendor's position is "I don't think these issues are critical enough to warrant a CVE ID ... because an attacker typically can't control when memory allocations fail."
Fix
Patch, vendor advisory and mitigation references on NVD 6
- http://www.openwall.com/lists/oss-security/2023/10/06/5 Mailing List, Patch, Third Party Advisory
- https://gitlab.gnome.org/GNOME/libxml2/-/issues/344 Issue Tracking, Patch, Vendor Advisory
- https://gitlab.gnome.org/GNOME/libxml2/-/issues/583 Issue Tracking, Patch, Vendor Advisory
- http://www.openwall.com/lists/oss-security/2023/10/06/5 Mailing List, Patch, Third Party Advisory
- https://gitlab.gnome.org/GNOME/libxml2/-/issues/344 Issue Tracking, Patch, Vendor Advisory
- https://gitlab.gnome.org/GNOME/libxml2/-/issues/583 Issue Tracking, Patch, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 6.5 · xmlsoftNVD modified 2026-10-15 00:16
Affected (CPE criteria) 1
cpe:2.3:a:xmlsoft:libxml2:*:*:*:*:*:*:*:*
References 8
- http://www.openwall.com/lists/oss-security/2023/10/06/5 Mailing List, Patch, Third Party Advisory
- https://gitlab.gnome.org/GNOME/libxml2/-/issues/344 Issue Tracking, Patch, Vendor Advisory
- https://gitlab.gnome.org/GNOME/libxml2/-/issues/583 Issue Tracking, Patch, Vendor Advisory
- http://www.openwall.com/lists/oss-security/2023/10/06/5 Mailing List, Patch, Third Party Advisory
- https://gitlab.gnome.org/GNOME/libxml2/-/issues/344 Issue Tracking, Patch, Vendor Advisory
- https://gitlab.gnome.org/GNOME/libxml2/-/issues/583 Issue Tracking, Patch, Vendor Advisory
- https://lists.debian.org/debian-lts-announce/2025/02/msg00028.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html