MediumGHSA-cpgf-5mjf-73p7CVE-2026-128068

rails-html-sanitizer: Possible regular expression denial of service with certain configurations

Published 13 Nov 2026 · Updated 13 Nov 2026

Is your project on an affected rails-html-sanitizer?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

Affected
>=1.0.3 <1.7.2
Fixed in
1.7.2
Update to the fixed version for your release line, for example:bundle update --conservative rails-html-sanitizer # Gemfile: '>= 1.7.2'

Details

Summary

Rails::HTML::PermitScrubber restricts the href and xlink:href attributes of SVG reference elements to local references. That check matched the attribute value against /^\s*[^#\s].*/m. In Ruby ^ anchors to every line start and \s matches newlines, so an all-whitespace value made the engine rescan the value from each of its line starts, taking time quadratic in its length.

  • Versions affected: >= 1.0.3, < 1.7.2
  • Not affected: < 1.0.3
  • Fixed versions: 1.7.2

Only Ruby 3.1 and earlier are affected. Ruby 3.2 added linear-time regexp matching, which makes the pattern linear.

Impact

An attacker who supplies HTML to be sanitized can consume CPU out of proportion to the input size, by sending an SVG reference element whose href or xlink:href is a long run of whitespace.

Applications are affected only when the allowed tags are overridden to include an SVG reference element such as use, along with href or xlink:href in the allowed attributes. The default allowed tags include no SVG elements, so the default configuration is not affected. Applications that use Loofah directly are exposed through its own copy of the check, fixed in Loofah 2.25.3.

Workarounds

Run Ruby 3.2 or later, which matches the pattern in linear time, or remove the SVG reference elements from the overridden allowed tags.

Credit

Reported by scyoon through the Rails HackerOne program.

Is GHSA-cpgf-5mjf-73p7 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected rails-html-sanitizer, and gives you the command that fixes it.

More advisories for rails-html-sanitizer

  • MediumCVE-2026-128069rails-html-sanitizer: Possible XSS via shared scrubber state in concurrent calls · 13 Nov 2026
  • MediumCVE-2026-73648Rails HTML Sanitizers: Possible XSS vulnerability with certain configurations · 21 Jul 2026
  • LowCVE-2024-53989rails-html-sanitizer has XSS vulnerability with certain configurations · 2 Dec 2024
  • LowCVE-2024-53987rails-html-sanitizer has XSS vulnerability with certain configurations · 2 Dec 2024
  • LowCVE-2024-53988rails-html-sanitizer has XSS vulnerability with certain configurations · 2 Dec 2024
  • LowCVE-2024-53986rails-html-sanitizer has XSS vulnerability with certain configurations · 2 Dec 2024
All 17 advisories for rails-html-sanitizer

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.