Sign in Sign up
JA · EN · FR
SecPulse
← Back
CVE-2026-44990 critical CVSS 9.3

Cross-Site Scripting (XSS) in sanitize-html (CVE-2026-44990)

Summary

cross-site scripting in sanitize-html (CVE-2026-44990). Confidential information can be exposed externally. Exploitable via ``xmp``. Mitigation: upgrade to `2.17.4` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2026-44990** has been found in sanitize-html. Attackers can target a specific entry point like ``xmp`` over the network to misuse the product. Confidential information can be exposed externally. CVSS score: 9.3/10. What to do: upgrade sanitize-html to **2.17.4** or later. If unsure, ask your IT team or search "sanitize-html CVE-2026-44990" on the vendor's site.
CVE-2026-44990 (sanitize-html) — CWE-79 / CVSS v3 9.3 Attack vector: remote (network-reachable) / unauthenticated Attack surface: `xmp` / `nonTextTags` / `script` / `style` Patched: `2.17.4` — 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
**Cross-site scripting (XSS)** (CWE-79) exists in sanitize-html. Attackers reach the vulnerable code path via ``xmp`` without authentication.
📍 Affected scope
sanitize-html — . Attack surface: `xmp` / `nonTextTags` / `script` / `style`.
🔥 Severity
Severity: Critical (CVSS 9.3/10). Confidential information can be exposed externally
🔧 How to fix
Update to **2.17.4**.
🛡️ 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 'sanitize-html' .` 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

  1. 1
    Identify exposure identify 
    grep -r 'sanitize-html' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `sanitize-html` を grep し、稼働しているサービス・バージョンを把握する。

  2. 6
    Apply patch patch 
    Upgrade sanitize-html to 2.17.4

    ステージング環境で 2.17.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。

  3. 7
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

npm sanitize-html
[{"type":"SEMVER","events":[{"introduced":"2.17.3"},{"fixed":"2.17.4"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →