Skip to content
Threat Brief

← All advisories

CVE-2026-126203

Medium 6.1No known exploitationFix available

Loofah: Mutation XSS in the HTML5 scrubbers through unescaped attribute values

Vendor advisory: GHSA-h6v6-rg66-fqj4

Record last updated

CVSS score

6.1

Medium on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.3%

Higher than 20% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

## Summary Loofah's HTML5 scrubbers could emit output that a browser parses into different markup, allowing mutation XSS. Nokogiri ` in attribute values. When the output contained certain MathML, a browser treated markup inside an allowed attribute as live HTML. The `:strip` scrubber is affected in every browser. The `:prune` and `:escape` scrubbers are affected in WebKit browsers such as Safari. Nokogiri 1.19.5 escapes ` ` in attribute values, as the HTML standard requires. Loofah 2.25.3 requires Nokogiri >= 1.19.5. ## Impact Applications that sanitize untrusted HTML with Loofah's HTML5 API (`Loofah.html5_fragment`, `Loofah.html5_document` and the `scrub_html5_*` methods) and display the result to other people are affected, including with the default allowlist. Not affected: Loofah's HTML4 API (including `Loofah::Helpers.sanitize`), the `:whitewash` scrubber, rails-html-sanitizer's default configuration, and JRuby. ## Mitigation Upgrade to Loofah >= 2.25.3, or upgrade Nokogiri to >= 1.19.5.

Weakness: CWE-79, CWE-116

Patching and mitigation

Patch status
Fix available (source: Microsoft MSRC)
Fix documented (source date)
Mitigation
None documented
Vendor guidance
msrc.microsoft.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
Microsoftazl4 rubygem-loofah 2.22.0-9.azl4 on Azure Linux 4.0Not documentedNot documentedMicrosoft MSRC
rubygemsloofahfrom 2.21.0 before 2.25.32.25.3GitHub Advisory Database

Timeline

  1. Advisory

    Microsoft advisory published

    Source: Microsoft MSRC (opens in a new tab)

  2. Patch

    Fix documented by Microsoft MSRC

    Source: Microsoft MSRC (opens in a new tab)

Vendor guidance and references