Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2026-73491

rubygem-loofah: Loofah: Cross-Site Scripting via malformed `javascript:` URI parsing

Overview

Published
12 Aug 2026
Modified
24 Oct 2026
Low CVE
1 Registry packages
21 OS packages
8 Linux distributions
Yes Fix available

Description

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: URIs whose scheme is split or prefixed with the HTML5 named whitespace character references 	 or 
. CGI.unescapeHTML leaves those references intact, so allowed_uri? reports the URL safe even though a browser decodes and strips the tab or line feed and executes the resulting javascript: URL. 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.

Source: OX vulnerability database

Severity

3.7 · LOW

CVSS 3.1 base score, scored by redhat.

Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N

Weakness: CWE-184

Affected packages · 1

Packages affected by CVE-2026-73491
EcosystemPackageVulnerableFixed in
RubyGems loofah >=2.25.0, <2.25.2 2.25.2

Open a package to see all its vulnerabilities.

Operating systems · 29 fixes

Red Hat 1 release · 1 package

affected 1
rubygem-loofah
Red Hat fixes for CVE-2026-73491
ReleasePackageFixed in
7 rubygem-loofah affected

SUSE Linux Enterprise 2 releases · 3 packages

fixed 4
hawk2 hawk-apiserver python313-pillow
SUSE Linux Enterprise fixes for CVE-2026-73491
ReleasePackageFixed inAdvisory
16.0 hawk2 2.7.2+git.1788518533.7d4dadd6-160000.1.1 SUSE-SU-2026:24195-1
16.1 hawk-apiserver 0.2.4+git.1792406875.6ed758a-160100.1.1 SUSE-SU-2026:24712-1
16.1 python313-pillow +1 11.3.0-160100.3.1 SUSE-SU-2026:24712-1
16.1 hawk2 2.7.2+git.1789128469.a738abc1-160100.1.1 SUSE-SU-2026:24712-1

chainguard 1 release · 12 packages

fixed 12
commercial-gitlab-rails-ee-19-2 gitlab-rails-ce-fips-19-3 gitlab-rails-ce-19-3 pghero ruby3-4-rails-7-2 ruby3-2-rails-7-2 +6
chainguard fixes for CVE-2026-73491
ReleasePackageFixed in
commercial-gitlab-rails-ee-19-2 +1 19.2.7-r4
gitlab-rails-ce-fips-19-3 19.3.1-r3
gitlab-rails-ce-19-3 19.3.1-r6
pghero +1 3.8.0-r4
ruby3-4-rails-7-2 7.2.3.1-r10
ruby3-2-rails-7-2 7.2.3.1-r8

6 more rows

debian 4 releases · 1 package

affected 3 fixed 1
ruby-loofah
debian fixes for CVE-2026-73491
ReleasePackageFixed in
11 ruby-loofah affected
12 ruby-loofah affected
13 ruby-loofah affected
14 ruby-loofah 2.25.2-1

echo 1 release · 1 package

affected 1
ruby-loofah
echo fixes for CVE-2026-73491
ReleasePackageFixed in
ruby-loofah affected

openSUSE 1 release · 1 package

fixed 1
hawk2
openSUSE fixes for CVE-2026-73491
ReleasePackageFixed inAdvisory
Tumbleweed hawk2 2.7.2+git.1792148770.648dcddb-1.1 openSUSE-SU-2026:12153-1

openSUSE Leap 2 releases · 2 packages

fixed 3
hawk2 hawk-apiserver
openSUSE Leap fixes for CVE-2026-73491
ReleasePackageFixed inAdvisory
16.0 hawk2 2.7.2+git.1788518533.7d4dadd6-160000.1.1 openSUSE-SU-2026:22068-1
16.1 hawk-apiserver 0.2.4+git.1792406875.6ed758a-160100.1.1 openSUSE-SU-2026:22305-1
16.1 hawk2 2.7.2+git.1789128469.a738abc1-160100.1.1 openSUSE-SU-2026:22305-1

wolfi 1 release · 3 packages

fixed 3
ruby4-0-rails-8-1 ruby3-4-rails-8-1 ruby3-2-rails-8-1
wolfi fixes for CVE-2026-73491
ReleasePackageFixed in
ruby4-0-rails-8-1 8.1.3-r10
ruby3-4-rails-8-1 8.1.3-r11
ruby3-2-rails-8-1 8.1.3-r9

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.