Skip to content
Threat Brief

← All advisories

CVE-2026-128069

Medium 4.7No known exploitationFix available

rails-html-sanitizer: Possible XSS via shared scrubber state in concurrent calls

Vendor advisory: GHSA-h7wh-q2qr-458c

Record last updated

CVSS score

4.7

Medium on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.2%

Higher than 13% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

rails-html-sanitizer is responsible for sanitizing HTML fragments in Rails applications. Before 1.7.2, the HTML4 and HTML5 variants of Rails::HTML::SafeListSanitizer reuse one Rails::HTML::PermitScrubber across calls and mutate its tags and attributes without synchronization. In a multithreaded process, concurrent sanitize calls using different tags: or attributes: options can interleave and cause one call to use the other call's allowlist. If a permissive call admits a script element or event-handler attribute, output expected to be sanitized under a stricter policy can retain it and cause cross-site scripting when rendered. Applications that are single-threaded, use one identical allowlist everywhere, or provide a separate scrubber: are not affected. This issue is fixed in version 1.7.2.

Weakness: CWE-79, CWE-362

Patching and mitigation

Patch status
Fix available (source: Microsoft MSRC)
Fix documented (source date)
Mitigation
None documented
Vendor guidance
msrc.microsoft.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
Microsoftazl4 rubygem-rails-html-sanitizer 1.6.0-8.azl4 on Azure Linux 4.0Not documentedNot documentedMicrosoft MSRC
railsrails-html-sanitizer< 1.7.2Not documentedCVE Program
rubygemsrails-html-sanitizerall versions before 1.7.21.7.2GitHub Advisory Database

Timeline

  1. Disclosure

    CVE record published by GitHub_M

    Source: CVE Program (opens in a new tab)

  2. Advisory

    Microsoft advisory published

    Source: Microsoft MSRC (opens in a new tab)

  3. Advisory change

    Microsoft advisory revised (2.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  4. Patch

    Fix documented by Microsoft MSRC

    Source: Microsoft MSRC (opens in a new tab)

Vendor guidance and references