CVE-2026-126209: Ruby loofah · From 2.25.0 until 2.25.3, 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 to Loofah version 2.25.3 or later, where this vulnerability is fixed. Since the issue is resolved in 2.25.3, applying this official fix is the recommended remediation. No other specific mitigations are indicated. Verify that your application does not rely on the vulnerable allowed_uri? method for sanitizing URIs or switch to using the default sanitize() method which is not affected.
Description
A vulnerability in the Ruby Loofah library versions from 2.25.0 up to but not including 2.25.3 allows a crafted URI to bypass sanitization checks in Loofah::HTML5::Scrub.allowed_uri?. This occurs because whitespace and control characters are stripped before decoding numeric character references without semicolons, which can hide javascript: or vbscript: schemes. This can lead to cross-site scripting (XSS) if the affected method is used to sanitize URIs in browser-interpreted attributes. The issue is fixed in version 2.25.3.
References
- ubuntu.com/security/CVE-2026-126209 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-126209 (opens in a new tab)
- github.com/flavorjones/loofah/commit/62c04841e8252a1b5373afcd2b89fb9b8279e317 (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-p9wj-w8xq-vjx6 (opens in a new tab)