Skip to main content
VulnerabilityPublished

CVE-2026-126206: flavorjones loofah · Cross-site Scripting

Affects flavorjones loofahSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.3 Medium · fixed in 2.25.3 : update flavorjones loofah when convenient.

Data as of 12 Nov 2026, 22:06 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 4.05.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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 12 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
flavorjonesloofahAffected
  • =2.25.2
Fixed in–

AI-suggested

Upgrade to loofah version 2.25.3 or later, where this vulnerability is fixed. Since the issue is resolved in the updated version, applying this official fix is the recommended remediation. No additional mitigation steps are indicated.

Description

CVE-2026-126206 is a cross-site scripting (XSS) vulnerability in the flavorjones loofah library version 2.25.2. The flaw arises from the Loofah::HTML5::Scrub.allowed_uri? method incorrectly treating a data URI mediatype containing the HTML5 named solidus reference / as malformed and falling back to text/plain, while browsers decode it as text/html. This discrepancy can allow an attacker to inject malicious scripts if user-controlled URLs validated by this helper are rendered in browser-interpreted URI attributes such as href. The default sanitize() method is not affected due to Nokogiri decoding entities before URI validation. The issue is fixed in version 2.25.3.

References

Community reviews

Loading reviews…