URI allows for userinfo Leakage in URI#join, URI#merge, and URI#+ (CVE-2025-27221)

Why this deserves its current priority

CVSS is 3.2. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps uri (rubygems), uri (rubygems), uri (rubygems), uri (rubygems). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
urirubygems	>=0 <0.11.3	0.11.3
urirubygems	>=0.12.0 <0.12.4	0.12.4
urirubygems	>=0.13.0 <0.13.2	0.13.2
urirubygems	>=1.0.0 <1.0.3	1.0.3

Recommended response

Check inventory. Check lockfiles and deployed manifests for uri, uri, uri.
Review the reported fix. Update uri to 0.11.3; uri to 0.12.4; uri to 0.13.2; uri to 1.0.3 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Mar 3, 2025
Evidence: source:osv:source_dates:source-dates:record
Source modified
Sep 10, 2026
Evidence: source:osv:source_dates:source-dates:record
First seen by HOL
Aug 8, 2026

Sources and claim methodology

Upstream source description

There is a possibility for userinfo leakage by in the uri gem. This vulnerability has been assigned the CVE identifier CVE-2025-27221. We recommend upgrading the uri gem. ## Details The methods `URI#join`, `URI#merge`, and `URI#+` retained userinfo, such as `user:password`, even after the host is replaced. When generating a URL to a malicious host from a URL containing secret userinfo using these methods, and having someone access that URL, an unintended userinfo leak could occur. Please update URI gem to version 0.11.3, 0.12.4, 0.13.2, 1.0.3 or later. ## Affected versions uri gem versions < 0.11.3, 0.12.0 to 0.12.3, 0.13.0, 0.13.1 and 1.0.0 to 1.0.2. ## Credits Thanks to Tsubasa Irisawa (lambdasawa) for discovering this issue. Also thanks to nobu for additional fixes of this vulnerability.

Quoted source text, attributed separately from HOL analysis.