CVE-2026-73492

Source
https://cve.org/CVERecord?id=CVE-2026-73492
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-73492.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2026-73492
Aliases
Downstream
Published
2026-08-12T21:00:24.679Z
Modified
2026-08-16T03:31:00.903177243Z
Severity
  • 2.3 (Low) CVSS_V4 - 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 CVSS Calculator
Summary
Loofah `allowed_uri?` does not detect `javascript:` URIs split by numeric character references without semicolons
Details

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.alloweduri? does not reject javascript: or vbscript: URIs whose scheme is split by semicolon-less numeric character references such as &#58, &#9, &#10, or &#13. CGI.unescapeHTML leaves these references encoded, so alloweduri? 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.

Database specific
{
    "cna_assigner": "GitHub_M",
    "cwe_ids": [
        "CWE-184",
        "CWE-79"
    ],
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/73xxx/CVE-2026-73492.json"
}
References

Affected packages

Git / github.com/flavorjones/loofah

Affected ranges

Type
GIT
Repo
https://github.com/flavorjones/loofah
Events
Database specific
Show details
{
    "extracted_events": [
        {
            "introduced": "2.25.0"
        },
        {
            "fixed": "2.25.2"
        }
    ],
    "source": [
        "AFFECTED_FIELD",
        "REFERENCES"
    ]
}

Affected versions

v2.*
v2.25.0
v2.25.1

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-73492.json"