← Back
CVE-2026-73648
Cross-Site Scripting (XSS) in rails-html-sanitizer (CVE-2026-73648)
Summary
cross-site scripting in rails-html-sanitizer (CVE-2026-73648). Risk of unauthorized operations or information disclosure. Exploitable via ``SVG_ALLOW_LOCAL_HREF``. Mitigation: upgrade to `1.7.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-73648** has been found in rails-html-sanitizer.
Attackers can target a specific entry point like ``SVG_ALLOW_LOCAL_HREF`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade rails-html-sanitizer to **1.7.1** or later.
If unsure, ask your IT team or search "rails-html-sanitizer CVE-2026-73648" on the vendor's site.
CVE-2026-73648 (rails-html-sanitizer) — CWE-79 /
Attack surface: `SVG_ALLOW_LOCAL_HREF` / `href` / `use` / `feImage`
Patched: `1.7.1` — apply immediately
Workaround: Remove the SVG reference elements (such as `use` and `feImage`) from the overridden allowed tags.
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 rails-html-sanitizer. Attackers reach the vulnerable code path via ``SVG_ALLOW_LOCAL_HREF`` without authentication.
📍 Affected scope
rails-html-sanitizer — . Attack surface: `SVG_ALLOW_LOCAL_HREF` / `href` / `use` / `feImage`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1.7.1**.
🛡️ Workaround
Workaround: Remove the SVG reference elements (such as `use` and `feImage`) from the overridden allowed tags.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'rails-html-sanitizer' .` 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 'rails-html-sanitizer' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `rails-html-sanitizer` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
Remove the SVG reference elements (such as `use` and `feImage`) from the overridden allowed tags.パッチが適用されるまでの応急処置として、Remove the SVG reference elements (such as `use` and `feImage`) from the overridden allowed tags. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade rails-html-sanitizer to 1.7.1ステージング環境で 1.7.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
rubygems
rails-html-sanitizer
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.7.1"}]}]