# CVE-2026-126209: Loofah allowed_uri? treats javascript: alert(1) as safe

> Attackers can bypass Loofah's URI sanitizer with encoded colons and scheme letters to enable javascript: links in Rails apps rendering approved values.

- **Severity:** Medium 5.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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Harmful if only installed:** No
- **Needs a specific call:** Yes (`Loofah::HTML5::Scrub.allowed_uri?`, `Rails::HTML::Sanitizer.allowed_uri?`)
- **Fix available:** Yes
- **Published:** 12 Nov 2026
- **Updated:** 12 Nov 2026
- **Also known as:** GHSA-p9wj-w8xq-vjx6

## What is CVE-2026-126209?

CVE-2026-126209 is a medium-severity cross-site scripting vulnerability in flavorjones loofah, published on 12 Nov 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation), CWE-184 (Incomplete List of Disallowed Inputs)

## Which versions are affected by CVE-2026-126209?

1 open source package ship an affected version, including loofah.

An affected version is only exploitable if your software calls Loofah::HTML5::Scrub.allowed_uri? or Rails::HTML::Sanitizer.allowed_uri?. Many projects that include it are not exposed.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `loofah` | RubyGems | From 2.25.0 | 2.25.3 |

## How do I fix CVE-2026-126209?

Upgrade loofah to 2.25.3 or later.

## Is CVE-2026-126209 being exploited?

There is no known exploitation of CVE-2026-126209 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-126209 and fix it if it is affected.

What it is: CVE-2026-126209 is a medium-severity cross-site scripting vulnerability in flavorjones loofah, published on 12 Nov 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-126209 in the wild and no public exploit code.
Exposure: An affected version is only exploitable if your software calls Loofah::HTML5::Scrub.allowed_uri? or Rails::HTML::Sanitizer.allowed_uri?. Many projects that include it are not exposed.

Affected packages and fixed versions:
- loofah (RubyGems): affected from 2.25.0; fixed in 2.25.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
   If an affected version is present, also search the code for calls to Loofah::HTML5::Scrub.allowed_uri? or Rails::HTML::Sanitizer.allowed_uri? and report whether any exist.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-126209/ (Markdown: https://insights.sbomify.com/CVE-2026-126209/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-126209
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-126209
- OSV: https://osv.dev/vulnerability/CVE-2026-126209

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-126209/
Summaries are generated and may contain mistakes; the official description above is the record.