Affected versions of this crate did not account for namespace-related parsing
differences between HTML, SVG, and MathML. Even if the
are not allowed, the underlying HTML parser still treats them differently.
Running cleanup without accounting for these differing namespaces resulted in an "impossible"
DOM, which appeared "safe" when examining the DOM tree, but when serialized and deserialized,
could be exploited to inject abitrary markup.
To exploit this, the application using this library must allow a tag that is parsed as raw text in HTML.
These elements are:
Applications that do not explicitly allow any of these tags should not be affected, since none are allowed by default.