How severe is CVE-2026-41673?

No CVSS score has been assigned to CVE-2026-41673 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-41673?

CVE-2026-41673 affects the following packages: @xmldom/xmldom (npm), @xmldom/xmldom (npm), xmldom (npm). Ecosystems affected: npm.

How do I fix CVE-2026-41673?

Update @xmldom/xmldom to 0.8.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-41673 is resolved across your whole dependency graph.

How do I detect CVE-2026-41673 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @xmldom/xmldom. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate CVE-2026-41673 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2026-41673?

O3 pinpoints whether CVE-2026-41673 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2026-41673 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-41673 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was CVE-2026-41673 published, and has it been updated?

CVE-2026-41673 was published on May 7, 2026 and was last updated on August 7, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

CVE-2026-41673

Fix: xmldom/xmldom@17678a2

CVE-2026-41673 is a security vulnerability in @xmldom/xmldom. O3 Security confirms whether CVE-2026-41673 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

xmldom: Denial of service via uncontrolled recursion in XML serialization

Also known asGHSA-2v35-w6hq-6mfw

Published

May 7, 2026

Updated

Aug 7, 2026

Affected

3 pkgs

Patched

2 / 3

Exploits

None indexed

Real-World Exposure

3 pkgs affected

📦@xmldom/xmldom📦@xmldom/xmldom📦xmldom

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

xmldom is a pure JavaScript W3C standard-based (XML DOM Level 2 Core) DOMParser and XMLSerializer module. In @xmldom/xmldom prior to versions 0.9.10 and 0.8.13 and xmldom version 0.6.0 and prior, seven recursive traversals in lib/dom.js operate without a depth limit. A sufficiently deeply nested DOM tree causes a RangeError: Maximum call stack size exceeded, crashing the application. This issue has been patched in versions @xmldom/xmldom versions 0.9.10 and 0.8.13.

Affected Packages

3 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@xmldom/xmldom`	all versions	0.8.13
📦npm	`@xmldom/xmldom`	≥ 0.9.0&&< 0.9.10	0.9.10
📦npm	`xmldom`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @xmldom/xmldom. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update @xmldom/xmldom to 0.8.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-41673 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2026-41673 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2026-41673. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

xmldom is a pure JavaScript W3C standard-based (XML DOM Level 2 Core) `DOMParser` and `XMLSerializer` module. In @xmldom/xmldom prior to versions 0.9.10 and 0.8.13 and xmldom version 0.6.0 and prior, seven recursive traversals in lib/dom.js operate without a depth limit. A sufficiently deeply nested DOM tree causes a RangeError: Maximum call stack size exceeded, crashing the application. This issue has been patched in versions @xmldom/xmldom versions 0.9.10 and 0.8.13.

O3 Security · Impact-Aware SCA

Is CVE-2026-41673 in your dependencies?

O3 detects CVE-2026-41673 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works