CVE-2026-126209: Loofah allowed_uri? treats javascript: alert(1) as safe
Summary Loofah::HTML5::Scrub.alloweduri? 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 alloweduri? strips, such as a space or tab. A browser ends the reference at that character and reads javascript: alert(1) as javascript: alert(1).
Published Nov 12, 2026
Affected packages
loofah
- Ecosystem
- RubyGems
- Affected
- >= 2.25.0, < 2.25.3
- Fixed in
- 2.25.3
- Check
bundle info loofah
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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: 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 : alert decodes as Ϊ (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 j\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.
References
- https://github.com/flavorjones/loofah/security/advisories/GHSA-p9wj-w8xq-vjx6
- https://github.com/flavorjones/loofah/pull/324
- https://github.com/flavorjones/loofah/commit/62c04841e8252a1b5373afcd2b89fb9b8279e317
- https://github.com/flavorjones/loofah/releases/tag/v2.25.3
- https://github.com/rubysec/ruby-advisory-db/blob/master/gems/loofah/GHSA-p9wj-w8xq-vjx6.yml
- https://github.com/advisories/GHSA-p9wj-w8xq-vjx6
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More RubyGems vulnerabilities
All RubyGems entriesCVE-2026-126203
Loofah: Mutation XSS in the HTML5 scrubbers through unescaped attribute values
medium6.1Nov 12, 2026CVE-2026-126205
Loofah: Regular expression denial of service in the SVG local-reference check
medium5.3Nov 12, 2026CVE-2026-126206
Loofah allowed_uri? treats data:text/html as safe text/plain
medium5.3Nov 12, 2026CVE-2026-126207
Loofah: CSS url() sanitization bypass via escaped parentheses
medium4.7Nov 12, 2026CVE-2026-126208
Loofah: SVG `<textPath>` and `<mpath>` bypass local-reference restriction
medium4.7Nov 12, 2026CVE-2026-73490
Loofah: SVG `href` attribute bypasses local-reference restriction
medium4.7Jul 21, 2026
