### Impactxmldom versions 0.6.0 and older do not correctly escape special characters when serializing elements removed from their ancestor. This may lead to unexpected syntactic changes during XML processing in some downstream applications.### PatchesUpdate to one of the fixed versions of `@xmldom/xmldom` (`>=0.7.0`)See issue #271 for the status of publishing `xmldom` to npm or join #270 for Q&A/discussion until it's resolved.### WorkaroundsDownstream applications can validate the input and reject the maliciously crafted documents.### ReferencesSimilar to this one reported on the Go standard library:- https://mattermost.com/blog/coordinated-disclosure-go-xml-vulnerabilities/- https://mattermost.com/blog/securing-xml-implementations-across-the-web/### For more informationIf you have any questions or comments about this advisory:* Open an issue in [`xmldom/xmldom`](https://github.com/xmldom/xmldom)* Email us: send an email to **all** addresses that are shown by `npm owner ls @xmldom/xmldom`