What is CVE-2026-73492?
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: or vbscript: URIs whose scheme is split by semicolon-less numeric character references such as :, 	, 
, or 
. CGI.unescapeHTML leaves these references encoded, so allowed_uri? reports the URL safe even though a browser decodes an encoded colon or strips encoded whitespace and executes the resulting URI scheme. 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.
The record classifies CVE-2026-73492 under weakness classes CWE-79, CWE-184. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 54 days ago.
Severity and exploitation probability
- CVSS v4.0 base score
- 2.3 — Low (derived from score)
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 - EPSS (FIRST)
- 0.2% probability of exploitation in the next 30 days, higher than 15.7% of all scored CVEs
- CISA KEV
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Threadlinqs priority
- 1.8/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- Published
- 2026-08-12
Is CVE-2026-73492 being exploited?
It currently carries a trending score of 33 in the Threadlinqs vulnerability feed.
Affected products and versions
- flavorjones: loofah
How to fix CVE-2026-73492
No vendor patch reference has been recorded for CVE-2026-73492 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.
Threat activity tracking CVE-2026-73492
No threat campaign in the Threadlinqs corpus currently references CVE-2026-73492, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.
Sources
Enriched from CVE.org, NVD, FIRST EPSS. Last verified by Threadlinqs on . This product uses the NVD API but is not endorsed or certified by the NVD.