Approved changes feed: RSS · Atom

cpe:2.3:a:xmldom_project:xmldom:0.9.0:beta1:*:*:*:node.js:*:*

part: a version: 0.9.0 update: beta1

VendorXmldom Project (f6acacf0-b8b2-5f84-a18b-a6ea811e5bdd)
ProductXmldom (6e033397-8eec-5186-b6a2-191f255490fc)
Edition*
Language*
Software edition*
Target softwarenode.js
Target hardware*
Other*

Notes

Imported from NVD CPE 2.0 feed

PURL mappings

PURLSourceLast updated
pkg:github/xmldom/xmldom purl2cpe 2026-06-01 10:15:42.821065
pkg:npm/%40xmldom/xmldom purl2cpe 2026-06-01 10:15:42.821067

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2022-39353 vulnerable 2026-06-08 05:47:18.644036 xmldom allows multiple root nodes in a DOM
CRITICAL (9.4)
xmldom is a pure JavaScript W3C standard-based (XML DOM Level 2 Core) `DOMParser` and `XMLSerializer` module. xmldom parses XML that is not well-formed because it contains multiple top level elements, and adds all root nodes to the `childNodes` collection of the `Document`, without reporting any error or throwing. This breaks the assumption that there is only a single root node in the tree, which led to issuance of CVE-2022-39299 as it is a potential issue for dependents. Update to @xmldom/xmldom@~0.7.7, @xmldom/xmldom@~0.8.4 (dist-tag latest) or @xmldom/xmldom@>=0.9.0-beta.4 (dist-tag next). As a workaround, please one of the following approaches depending on your use case: instead of searching for elements in the whole DOM, only search in the `documentElement`or reject a document with a document that has more then 1 `childNode`.
Published: 2022-11-02T00:00:00.000Z
Updated: 2025-04-22T17:16:38.092Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2022-37616 vulnerable 2026-06-08 05:47:12.961900 Details available
A prototype pollution vulnerability exists in the function copy in dom.js in the xmldom (published as @xmldom/xmldom) package before 0.8.3 for Node.js via the p variable. NOTE: the vendor states "we are in the process of marking this report as invalid"; however, some third parties takes the position that "A prototype injection/Prototype pollution is not just when global objects are polluted with recursive merge or deep cloning but also when a target object is polluted."
Published: 2022-10-11T00:00:00.000Z
Updated: 2024-08-03T10:29:21.029Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.

Inspect record JSON

Open JSON directly

Open this panel to browse, search, copy or download the JSON record.