CVE-2026-126206: medium-severity vulnerability in flavorjones loofah
Loofah allowed_uri? treats data:text/html as safe text/plain
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 5.3epss 0.4%
Loofah is a general library for manipulating and transforming HTML/XML documents and fragments, built on top of Nokogiri. In 2.25.2, Loofah::HTML5::Scrub.allowed_uri? treats a data URI mediatype containing the HTML5 named solidus reference / as malformed and falls back to the allowed text/plain, while a browser decodes the reference and interprets the same value as text/html. An application that validates a user-controlled URL with this helper and renders the approved value in href or another browser-interpreted URI attribute can allow cross-site scripting. Rails::HTML::Sanitizer.allowed_uri? re-exports the affected helper. Loofah's default sanitize() path is not affected because Nokogiri decodes the entity before URI validation. This issue is fixed in version 2.25.3.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N
Affected products
flavorjones · loofahRelated CVEs — flavorjones loofah
In the same product, most dangerous first.
CVE-2022-23514HIGHInefficient Regular Expression Complexity in LoofahEPSS 1.8%CVE-2022-23516HIGHUncontrolled Recursion in LoofahEPSS 1.2%CVE-2022-23515MEDIUMImproper neutralization of data URIs may allow XSS in LoofahEPSS 0.9%CVE-2026-126209MEDIUMLoofah allowed_uri? treats javascript: alert(1) as safeEPSS 0.4%CVE-2026-126205MEDIUMLoofah: Regular expression denial of service in the SVG local-reference checkEPSS 0.4%CVE-2026-73492LOWLoofah `allowed_uri?` does not detect `javascript:` URIs split by numeric character references without semicolonsEPSS 0.4%