Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-p9wj-w8xq-vjx6 | Loofah allowed_uri? treats javascript: alert(1) as safe |
Thu, 12 Nov 2026 21:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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.3, Loofah::HTML5::Scrub.allowed_uri? strips whitespace and control characters before decoding a semicolon-less numeric character reference, changing where the reference ends and hiding a javascript: or vbscript: scheme that a browser reconstructs. The bypass applies to encoded colons and encoded scheme letters when a stripped character terminates the numeric reference. An application that renders the approved value in href or another browser-interpreted URI attribute can allow cross-site scripting, and Rails::HTML::Sanitizer.allowed_uri? re-exports the affected helper. Loofah's default sanitize() path is not affected because Nokogiri decodes entities before URI evaluation. This issue is fixed in version 2.25.3. | |
| Title | Loofah allowed_uri? treats javascript: alert(1) as safe | |
| Weaknesses | CWE-184 CWE-79 |
|
| References |
| |
| Metrics |
cvssV4_0
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-11-12T21:01:58.128Z
Reserved: 2026-11-10T20:07:44.958Z
Link: CVE-2026-126209
No data.
Status : Received
Published: 2026-11-12T21:17:22.210
Modified: 2026-11-12T21:17:22.210
Link: CVE-2026-126209
No data.
OpenCVE Enrichment
No data.
Github GHSA