← Back
CVE-2026-41673
high
CVSS 7.5
Vulnerability in @xmldom/xmldom (CVE-2026-41673)
Summary
vulnerability in @xmldom/xmldom (CVE-2026-41673). Risk of unauthorized operations or information disclosure. Exploitable via ``node.textContent``. Mitigation: upgrade to `0.9.10` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-41673** has been found in @xmldom/xmldom.
Attackers can target a specific entry point like ``node.textContent`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade @xmldom/xmldom to **0.9.10** or later.
If unsure, ask your IT team or search "@xmldom/xmldom CVE-2026-41673" on the vendor's site.
CVE-2026-41673 (@xmldom/xmldom) — CWE-674 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `node.textContent` / `RangeError` / `serializeToString` / `_visitNode`
Patched: `0.9.10` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-674) exists in @xmldom/xmldom. Attackers reach the vulnerable code path via ``node.textContent`` without authentication.
📍 Affected scope
@xmldom/xmldom — . Attack surface: `node.textContent` / `RangeError` / `serializeToString` / `_visitNode`.
🔥 Severity
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.9.10**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r '@xmldom/xmldom' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@xmldom/xmldom' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `@xmldom/xmldom` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade @xmldom/xmldom to 0.9.10ステージング環境で 0.9.10 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
@xmldom/xmldom
[{"type":"SEMVER","events":[{"introduced":"0.9.0"},{"fixed":"0.9.10"}]}]
npm
xmldom
[{"type":"SEMVER","events":[{"introduced":"0"},{"last_affected":"0.6.0"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-41673
- package https://github.com/xmldom/xmldom
- web 134c704f-9b21-4f2e-91b3-4a467353bcc0
- web [email protected]
- web [email protected]
- web [email protected]
- web [email protected]
- web [email protected]
- web [email protected]
- web [email protected]
- web [email protected]
- web [email protected]
- web [email protected]
- web [email protected]
- web https://github.com/advisories/GHSA-2v35-w6hq-6mfw
- web 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
- web 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
- web 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
- web 0b0ca135-0b70-47e7-9f44-1890c2a1c46c