CVE-2022-37616

unknown

Published 2022-10-11 · Modified 2026-03-13

💬 Discuss on Community ✚ Propose mitigation

CVSS v3

—

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CVSS v4 NEW

—

not yet in upstream

VIR risk

—

Description

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."

Predictions

Exploit likelihood

30%

Patch ETA

—

Heuristic predictions, AS-IS, for prioritization only.

Mitigations

No mitigations published for this CVE yet.

The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.

✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here with source_tier=community-verified.

OS impact

OS	Version	Status	Fixed in
debian	bookworm	fixed	`0.8.3-1`
debian	bullseye	fixed	`0.5.0-1+deb11u1`
debian	forky	fixed	`0.8.3-1`
debian	sid	fixed	`0.8.3-1`
debian	trixie	fixed	`0.8.3-1`

Package impact

Ecosystem	Package	Vulnerable	Fixed
npm	@xmldom/xmldom	`>=0.8.0,<0.8.3`	`0.8.3`
npm	xmldom	`<=0.6.0`
npm	@xmldom/xmldom	`>=0.9.0-beta.1,<0.9.0-beta.2`	`0.9.0-beta.2`
npm	@xmldom/xmldom	`<0.7.6`	`0.7.6`

References

Community-verified mitigations for this CVE will appear above when contributors publish them.

Verify integrity in audit chain (admin only). AS-IS.