dom-iterator code execution vulnerabilityGHSA-jrvm-mcxc-mf6m
HIGHFix: matthewmueller/dom-iterator@9e0e0faGHSA-jrvm-mcxc-mf6m is a high-severity (CVSS 7.3) Code Injection vulnerability in dom-iterator. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for dom-iterator — see the affected versions and patch details below.
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
Exploitation and automatability from CISA’s SSVC triage for GHSA-jrvm-mcxc-mf6m.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
dom-iteratornpmDescription
Versions of the package dom-iterator before 1.0.1 are vulnerable to Arbitrary Code Execution due to use of the Function constructor without complete input sanitization. Function generates a new function body and thus care must be given to ensure that the inputs to Function are not attacker-controlled. The risks involved are similar to that of allowing attacker-controlled input to reach eval.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | dom-iterator | all versions | 1.0.1npm install dom-iterator@1.0.1 |
Affected Products
dom-iteratormatthewmuellerResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for dom-iterator, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update dom-iterator to 1.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jrvm-mcxc-mf6m is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.
Frequently Asked Questions
Is GHSA-jrvm-mcxc-mf6m in your dependencies?
Find it across npm, including transitive dependencies.