CVE-2026-126206: Ruby loofah · In 2.25.2, Loofah::HTML5::Scrub.allowed_uri?
Affects ruby-loofahSource GCVE Database
Not known to be exploited · CVSS 5.3 Medium · fixed in 2.25.3 : update ruby-loofah when convenient.
Data as of 18 Nov 2026, 16:22 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 4.0 | 5.3 |
|---|
- Patch
- Available – fixed in 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:NExploitation evidence
Disclosed: evidence found.
CVE published 12 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.10ruby-loofahpkg:deb/ubuntu/ruby-loofah?arch=source&distro=stonkingOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSruby-loofahpkg:deb/ubuntu/ruby-loofah?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 24.04 LTSruby-loofahpkg:deb/ubuntu/ruby-loofah?arch=source&distro=nobleOther threats | Affected
| Fixed in– |
Ubuntu 22.04 LTSruby-loofahpkg:deb/ubuntu/ruby-loofah?arch=source&distro=jammyOther threats | Affected
| Fixed in– |
Ubuntu 20.04 LTSruby-loofahpkg:deb/ubuntu/ruby-loofah?arch=source&distro=focalOther threats | Affected
| Fixed in– |
Ubuntu 18.04 LTSruby-loofahpkg:deb/ubuntu/ruby-loofah?arch=source&distro=bionicOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade Loofah to version 2.25.3 or later, where this issue is fixed. Applications using Rails::HTML::Sanitizer.allowed_uri? should also benefit from this fix. No other mitigation steps are indicated as the default sanitize() method is not affected.
Description
Loofah versions up to 2.25.2 contain a vulnerability in the HTML5 URI validation helper Loofah::HTML5::Scrub.allowed_uri?. This helper incorrectly treats data URI mediatypes containing the HTML5 named solidus reference / as malformed and falls back to text/plain, whereas browsers decode this reference as text/html. Applications that validate user-controlled URLs with this helper and render them in browser-interpreted URI attributes may be vulnerable to cross-site scripting (XSS). The default sanitize() method is not affected due to Nokogiri's decoding behavior. The issue is fixed in Loofah version 2.25.3.
References
- ubuntu.com/security/CVE-2026-126206 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-126206 (opens in a new tab)
- github.com/flavorjones/loofah/commit/ad92002966053309f83b550861e2ef04bc714744 (opens in a new tab)
- github.com/flavorjones/loofah/pull/324 (opens in a new tab)
- github.com/flavorjones/loofah/releases/tag/v2.25.3 (opens in a new tab)
- github.com/flavorjones/loofah/security/advisories/GHSA-jcff-cj73-4w4f (opens in a new tab)