Vulnerability in @rootio/sanitize-html (ROOT-APP-NPM-CVE-2026-44990)

Summary

vulnerability in @rootio/sanitize-html (ROOT-APP-NPM-CVE-2026-44990). Confidential information can be exposed externally. Mitigation: upgrade to `2.17.2-root.io.1, 2.12.1-root.io.1, 2.12.1-root.io.2, 2.17.2-root.io.2` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **ROOT-APP-NPM-CVE-2026-44990** has been found in @rootio/sanitize-html. Confidential information can be exposed externally. CVSS score: ?/10. What to do: upgrade @rootio/sanitize-html to **2.17.2-root.io.1, 2.12.1-root.io.1, 2.12.1-root.io.2, 2.17.2-root.io.2** or later. If unsure, ask your IT team or search "@rootio/sanitize-html ROOT-APP-NPM-CVE-2026-44990" on the vendor's site.

ROOT-APP-NPM-CVE-2026-44990 (@rootio/sanitize-html) — Attack vector: remote (network-reachable) / unauthenticated Patched: `2.17.2-root.io.1, 2.12.1-root.io.1, 2.12.1-root.io.2, 2.17.2-root.io.2` — 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** (unclassified) exists in @rootio/sanitize-html.

📍 Affected scope

@rootio/sanitize-html — .

🔥 Severity

Severity: ?. Confidential information can be exposed externally

🔧 How to fix

Update to **2.17.2-root.io.1, 2.12.1-root.io.1, 2.12.1-root.io.2, 2.17.2-root.io.2**.

🛡️ 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 '@rootio/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
Identify exposure identify
```
grep -r '@rootio/sanitize-html' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `@rootio/sanitize-html` を grep し、稼働しているサービス・バージョンを把握する。
6
Apply patch patch
```
Upgrade @rootio/sanitize-html to 2.17.2-root.io.1, 2.12.1-root.io.1, 2.12.1-root.io.2, 2.17.2-root.io.2
```
ステージング環境で 2.17.2-root.io.1, 2.12.1-root.io.1, 2.12.1-root.io.2, 2.17.2-root.io.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
7
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

Root:npm @rootio/sanitize-html

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.17.2-root.io.1"},{"fixed":"2.12.1-root.io.1"},{"fixed":"2.12.1-root.io.2"},{"fixed":"2.17.2-root.io.2"}]}]

Root:npm sanitize-html

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.12.1-aikido.2"},{"fixed":"2.17.2-aikido.2"}]}]

Summary

AI summary snake-internal / snake-material-v2

Response Actions (7 steps)

Affected packages

🍪 About cookies