Cross-site Scripting (XSS) Affecting ruby-rails-html-sanitizer package, versions *


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.22% (13th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-DEBIAN13-RUBYRAILSHTMLSANITIZER-22550239
  • published15 Nov 2026
  • disclosed13 Nov 2026

Introduced: 13 Nov 2026

NewCVE-2026-128069  (opens in a new tab)
CWE-79  (opens in a new tab)
CWE-362  (opens in a new tab)

How to fix?

There is no fixed version for Debian:13 ruby-rails-html-sanitizer.

NVD Description

Note: Versions mentioned in the description apply only to the upstream ruby-rails-html-sanitizer package and not the ruby-rails-html-sanitizer package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

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.