{"answers":{"affected":"2 open source packages ship an affected version, including loofah.","exploited":"There is no known exploitation of CVE-2026-73492 in the wild and no public exploit code.","fix":"Upgrade loofah to 2.25.2 or later.","what":"CVE-2026-73492 is a low-severity cross-site scripting vulnerability in flavorjones loofah, published on 12 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-73492 and fix it if it is affected.\n\nWhat it is: CVE-2026-73492 is a low-severity cross-site scripting vulnerability in flavorjones loofah, published on 12 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-73492 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- loofah (RubyGems): affected from 2.25.0; fixed in 2.25.2\n- loofah (RubyGems): affected from 2.25.0; fixed in 2.25.2\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-73492/ (Markdown: https://insights.sbomify.com/CVE-2026-73492/index.md)","id":"CVE-2026-73492","markdown":"https://insights.sbomify.com/CVE-2026-73492/index.md","name":"CVE-2026-73492","record":{"aliases":["DEBIAN-CVE-2026-73492","GHSA-5qhf-9phg-95m2","UBUNTU-CVE-2026-73492"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"Ruby HTML sanitization library","requires_auth":"low_privilege","summary":"Attackers can bypass URI sanitization in Loofah by using encoded characters, leading to XSS if HTML-encoded strings are passed directly to allowed_uri?.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":2.3,"severity":"low","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"},{"id":"CWE-184","name":"Incomplete List of Disallowed Inputs"}],"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: or vbscript: URIs whose scheme is split by semicolon-less numeric character references such as \u0026#58, \u0026#9, \u0026#10, or \u0026#13. 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.","ecosystems":["RubyGems"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Loofah `allowed_uri?` does not detect `javascript:` URIs split by numeric character references without semicolons","id":"CVE-2026-73492","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"RubyGems","product":null,"products":[],"type":"xss","year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"http4s-blaze-server: Unbounded WebSocket message aggregation","id":"CVE-2026-73493"},"packages":[{"ecosystem":"RubyGems","fixed":["2.25.2"],"introduced":["2.25.0"],"last_affected":[],"package":"loofah","purl":null,"source":"GHSA-5qhf-9phg-95m2"},{"ecosystem":"RubyGems","fixed":["2.25.2"],"introduced":["2.25.0"],"last_affected":[],"package":"loofah","purl":"pkg:gem/loofah","source":"GHSA-5qhf-9phg-95m2"}],"prev":{"headline":"Loofah `allowed_uri?` does not detect `javascript:` URIs split by named whitespace character references","id":"CVE-2026-73491"},"products":["loofah"],"published":"2026-08-12","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-14","vendors":["flavorjones"]},"summary":"Attackers can bypass URI sanitization in Loofah by using encoded characters, leading to XSS if HTML-encoded strings are passed directly to allowed_uri?.","url":"https://insights.sbomify.com/CVE-2026-73492/"}