CVE-2026-73492 flavorjones CVE debrief

Who should care

Defenders responsible for systems using Loofah for HTML/XML document manipulation should assess exposure and prioritize verification and updates to prevent potential code execution. This includes operators, platform administrators, vulnerability management teams, and security teams who need to review and adjust code using Loofah::HTML5::Scrub.allowed_uri? to ensure safe usage.

Why it matters

Defenders should prioritize verifying and updating Loofah to version 2.25.2 due to a URI scheme bypass issue. Affected versions (2.25.0-2.25.1) may allow attackers to execute arbitrary code. Systems using Loofah for HTML/XML document manipulation should assess exposure and adjust code using Loofah::HTML5::Scrub.allowed_uri? to ensure safe usage.

• Potential for attackers to execute arbitrary JavaScript or VBScript code in affected systems
• Bypass of URI scheme restrictions in Loofah::HTML5::Scrub.allowed_uri?
• Possible impact on systems relying on Loofah for HTML/XML document sanitization

Technical summary

The Loofah::HTML5::Scrub.allowed_uri? method does not properly reject javascript: or vbscript: URIs when the scheme is split by semicolon-less numeric character references such as &#58, &#9, &#10, or &#13. This issue affects callers that pass HTML-encoded strings directly to allowed_uri?. The default sanitize() path in Loofah is not affected. Official references are available from the Loofah repository and CVE Program, confirming the fix in version 2.25.2. Defenders should prioritize verifying and updating Loofah to version 2.25.2 if using affected versions.

Defensive priority

Defenders should prioritize verifying and updating Loofah to version 2.25.2 if using affected versions (2.25.0-2.25.1) and assess exposure in systems using Loofah for HTML/XML document manipulation.

Recommended defensive actions

• Verify Loofah version and update to 2.25.2 if using affected versions (2.25.0-2.25.1)
• Assess exposure in systems using Loofah for HTML/XML document manipulation
• Review and adjust code using Loofah::HTML5::Scrub.allowed_uri? to ensure safe usage
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The issue is fixed in Loofah version 2.25.2. Official references are available from the Loofah repository and CVE Program. The vulnerability affects Loofah versions 2.25.0-2.25.1. Defenders should verify Loofah version and update to 2.25.2 if using affected versions. The default sanitize() path in Loofah is not affected. Evidence limits suggest focusing on source-grounded technical framing and defensive priorities.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.