← Back
CVE-2025-61594
Information Disclosure in uri (CVE-2025-61594)
Summary
vulnerability in uri (CVE-2025-61594). Confidential information can be exposed externally. Exploitable via ``uri``. Mitigation: upgrade to `1.0.4` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2025-61594** has been found in uri.
Attackers can target a specific entry point like ``uri`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: ?/10.
What to do: upgrade uri to **1.0.4** or later.
If unsure, ask your IT team or search "uri CVE-2025-61594" on the vendor's site.
CVE-2025-61594 (uri) — CWE-200 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `uri`
Patched: `1.0.4` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**information disclosure** (CWE-200) exists in uri. Attackers reach the vulnerable code path via ``uri`` without authentication.
📍 Affected scope
uri — . Attack surface: `uri`.
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to **1.0.4**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'uri' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'uri' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `uri` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade uri to 1.0.4ステージング環境で 1.0.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
RubyGems
uri
[{"type":"ECOSYSTEM","events":[{"introduced":"1.0.0"},{"fixed":"1.0.4"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2025-61594
- advisory https://github.com/advisories/GHSA-22h5-pq3x-2gf2
- package https://github.com/ruby/uri
- web https://github.com/ruby/uri/security/advisories/GHSA-j4pr-3wm6-xx2r
- web https://github.com/ruby/uri/commit/20157e3e29b125ff41f1d9662e2e3b1d066f5902
- web https://github.com/ruby/uri/commit/7e521b2da0833d964aab43019e735aea674e1c2c
- web https://github.com/ruby/uri/commit/d3116ca66a3b1c97dc7577f9d2d6e353f391cd6a
- web https://hackerone.com/reports/2957667
- web https://github.com/rubysec/ruby-advisory-db/blob/master/gems/uri/CVE-2025-61594.yml
- web https://www.ruby-lang.org/en/news/2025/02/26/security-advisories
- web https://www.ruby-lang.org/en/news/2025/10/07/uri-cve-2025-61594