Skip to main content
VulnerabilityPublished

CVE-2026-73491: flavorjones loofah · Incomplete List of Disallowed Inputs

Affects flavorjones loofahSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 2.3 Low : upgrade to 2.25.2 when convenient.

Data as of 10 Nov 2026, 23:24 UTC

CVSS 4.0 base score
2.3Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.25.2
CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Aug 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 10 Nov 2026.

What to do

Upgrade flavorjones loofah to 2.25.2.

Affected software

ProductAffectedFixed in
flavorjonesloofahAffected
  • >=2.25.0 <2.25.2
Fixed in
  • 2.25.2
RubyGemsloofahpkg:gem/loofahOther threatsAffected
  • <2.25.2 >=2.25.0
Fixed in
  • 2.25.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade to loofah version 2.25.2 or later, where this issue is fixed. If upgrading is not immediately possible, avoid passing HTML-encoded strings directly to allowed_uri? and instead use the default sanitize() method, which is not affected by this vulnerability. Patch status is confirmed fixed in version 2.25.2.

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 &Tab; or &NewLine;. 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.

References

Community reviews

Loading reviews…