MediumGHSA-p9wj-w8xq-vjx6CVE-2026-126209

Loofah allowed_uri? treats javascript&#x3a alert(1) as safe

Published 12 Nov 2026 · Updated 12 Nov 2026

Is your project on an affected loofah?

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

loofahRubyGems
Affected
>=2.25.0 <2.25.3
Fixed in
2.25.3
Update to the fixed version for your release line, for example:bundle update --conservative loofah # Gemfile: '>= 2.25.3'

Details

Summary

Loofah::HTML5::Scrub.allowed_uri? returns true for a javascript: or vbscript: URI whose scheme is split by a numeric character reference without a trailing semicolon, followed by a character that allowed_uri? strips, such as a space or tab. A browser ends the reference at that character and reads javascript&#x3a alert(1) as javascript: alert(1).

Details

allowed_uri? strips control characters and whitespace before it decodes numeric character references. Removing the character that ends a semicolon-less reference lets the reference run on into the following text, so &#x3a alert decodes as &#x3aa (U+03AA) instead of a colon, and no scheme is detected. The same applies to decimal references and to references that encode a scheme letter, as in &#x6a\tavascript:alert(1).

Loofah's default sanitize() path is not affected, because Nokogiri decodes the entity during parsing before Loofah evaluates the URI. This issue affects only callers of the public allowed_uri? string-level helper that pass it HTML-encoded strings.

Impact

Applications that validate a user-controlled URL with Loofah::HTML5::Scrub.allowed_uri? and then render the approved value into an href or another browser-interpreted URI attribute may be vulnerable to cross-site scripting. Rails::HTML::Sanitizer.allowed_uri? re-exports the same helper.

Mitigation

Upgrade to Loofah >= 2.25.3.

Credit

Responsibly reported by GitHub user @manus-pi.

Is GHSA-p9wj-w8xq-vjx6 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 loofah, and gives you the command that fixes it.

More advisories for loofah

  • MediumCVE-2026-126208Loofah: SVG `<textPath>` and `<mpath>` bypass local-reference restriction · 12 Nov 2026
  • MediumCVE-2026-126207Loofah: CSS url() sanitization bypass via escaped parentheses · 12 Nov 2026
  • MediumCVE-2026-126205Loofah: Regular expression denial of service in the SVG local-reference check · 12 Nov 2026
  • MediumCVE-2026-126206Loofah allowed_uri? treats data:text&sol;html as safe text/plain · 12 Nov 2026
  • MediumCVE-2026-126203Loofah: Mutation XSS in the HTML5 scrubbers through unescaped attribute values · 12 Nov 2026
  • LowCVE-2026-73492Loofah `allowed_uri?` does not detect `javascript:` URIs split by numeric character references without semicolons · 21 Jul 2026
All 17 advisories for loofah

References

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