UriApplication · Ruby Lang
CVE-2025-61594
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedURI is a module providing classes to handle Uniform Resource Identifiers. In versions 0.12.4 and earlier (bundled in Ruby 3.2 series) 0.13.2 and earlier (bundled in Ruby 3.3 series), 1.0.3 and earlier (bundled in Ruby 3.4 series), when using the + operator to combine URIs, sensitive information like passwords from the original URI can be leaked, violating RFC3986 and making applications vulnerable to credential exposure. This is a a bypass for the fix to CVE-2025-27221 that can expose user credentials. This issue has been fixed in versions 0.12.5, 0.13.3 and 1.0.4.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe URI gem for Ruby has a vulnerability where using the + operator to combine URIs leaks sensitive password information from the original URI, violating RFC3986 and exposing credentials. This is a bypass of the previous fix for CVE-2025-27221.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
UriApplication
< 0.12.5>= 0.13.0, < 0.13.3>= 1.0.0, < 1.0.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed URI gem versionRun `ruby -e "require 'uri'; puts URI::VERSION"` or `gem list uri` to retrieve the version numberAffected if Version is < 0.12.5, >= 0.13.0 and < 0.13.3, or >= 1.0.0 and < 1.0.4
-
Test password leakage via the + operatorExecute: ruby -e "require 'uri'; u = URI('http://user:[email protected]'); combined = u + '/path'; puts combined.to_s" - observe if the password 'secret' appears in the combined URI outputAffected if The password from the original URI is visible in the combined URI string (should be redacted but is not)
-
Verify if code uses URI + operator with authenticated URIsSearch codebase for patterns like `uri +` or `URI(...) +` where the URI contains credentials in the format `user:password@host`Affected if Code combines URIs containing embedded credentials using the + operator
You are affected if your URI gem version is in the vulnerable range AND your code uses the + operator to combine URIs that contain passwords, resulting in password leakage in the output.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped0.12.50.13.31.0.4
Upgrade the URI gem to version 0.12.5 (Ruby 3.2), 0.13.3 (Ruby 3.3), or 1.0.4 (Ruby 3.4), or update to a Ruby version that bundles the patched gem.
uri gem version 0.12.5, 0.13.3, or 1.0.4 (matching your Ruby series)
- Identify the Ruby URI gem version in your project by checking your Gemfile.lock for the 'uri' gem
- Run 'bundle update uri' to update to the latest compatible version, or specify the fixed version in your Gemfile (gem "uri", "~> 0.12.5" for 0.12.x, "~> 0.13.3" for 0.13.x, or "~> 1.0.4" for 1.0.x)
- Run 'bundle install' to install the updated gem
- Restart any running Ruby processes to ensure the new gem version is loaded
- Verify the installed uri gem version using 'bundle exec gem list uri' to confirm the fix is applied
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Uri
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-61594 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-61594 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data