ManageIQ / ManageIQ/miq_bot

CVE-2026-73492 (Medium) detected in loofah-2.25.1.gem

Open Beginner friendly
#970 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Mend: dependency security vulnerability
Dominant language
Ruby
Stars
16
Forks
39
Avg merge
1d 11h
Merged PRs (30d)
8

Description

## CVE-2026-73492 - Medium Severity Vulnerability
Vulnerable Library - loofah-2.25.1.gem

Loofah is a general library for manipulating and transforming HTML/XML documents and fragments,
built on top of Nokogiri.

Loofah also includes some HTML sanitizers based on `html5lib`'s safelist, which are a specific
application of the general transformation functionality.


Library home page: https://rubygems.org/gems/loofah-2.25.1.gem


Sample Path to Dependency File: /Gemfile.lock


Path to vulnerable library: /tmp/containerbase/cache/.ruby/cache/loofah-2.25.1.gem


Dependency Hierarchy:
- rails-8.0.5.gem (Root Library)
- activestorage-8.0.5.gem
- actionpack-8.0.5.gem
- actionview-8.0.5.gem
- rails-html-sanitizer-1.7.0.gem
- :x: **loofah-2.25.1.gem** (Vulnerable Library)

Found in base branch: master



Vulnerability 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.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.

Publish Date: 2026-08-12

URL: CVE-2026-73492



CVSS 3 Score Details (4.9)

Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None


For more information on CVSS3 Scores, click here.


Suggested Fix

Type: Upgrade version


Origin: https://github.com/flavorjones/loofah/security/advisories/GHSA-5qhf-9phg-95m2


Release Date: 2026-08-12


Fix Resolution: loofah - 2.25.2,https://github.com/flavorjones/loofah.git - v2.25.2

***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with Gemfile.lock and the listed Rails dependency chain to see how loofah-2.25.1 is resolved. Update the dependency to loofah 2.25.2, then confirm the lockfile no longer resolves the vulnerable version and the reported vulnerability is addressed.

Written by the indexing model from the issue text.

Assessment

Tech stack
rails, ruby
Domain
security
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
85/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.