CVE-2026-73492 PUBLISHED

Loofah `allowed_uri?` does not detect `javascript:` URIs split by numeric character references without semicolons

Assigner: GitHub_M
Reserved: 12.08.2026 Published: 12.08.2026 Updated: 12.08.2026

Loofah is a general library for manipulating and transforming HTML/XML documents and fragments, built on top of Nokogiri. From 2.25.0 until 2.25.2, Loofah::HTML5::Scrub.allowed_uri? does not reject javascript: or vbscript: URIs whose scheme is split by semicolon-less numeric character references such as :, , , or . CGI.unescapeHTML leaves these references encoded, so allowed_uri? reports the URL safe even though a browser decodes an encoded colon or strips encoded whitespace and executes the resulting URI scheme. This issue affects only callers that pass HTML-encoded strings directly to allowed_uri?; Loofah's default sanitize() path is not affected. This issue is fixed in version 2.25.2.

Metrics

CVSS Vector: CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N
CVSS Score: 2.3

Product Status

Vendor flavorjones
Product loofah
Versions
  • Version >= 2.25.0, < 2.25.2 is affected

References

Problem Types

  • CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') CWE
  • CWE-184: Incomplete List of Disallowed Inputs CWE