CVE-2025-27221VulnerabilityPublished 3 Mar 2025Updated 3 Nov 2025

CVE-2025-27221: ruby-lang URI · Improper Removal of Sensitive Information Before Storage or Transfer

Affects ruby-lang URISource CVE Database V5

Not known to be exploited · CVSS 3.2 Low.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

3.2Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N

Attack Vector: Local
Attack Complexity: High
Privileges Required: None
User Interaction: None
Scope: Changed
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 3 Mar 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
RubyGemsuri`pkg:gem/uri`Other threats	Affected =0 =0.12.0 =0.13.0 =1.0.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Upgrade the Ruby URI gem to version 1.0.3 or later immediately to ensure the vulnerability is patched. 2. Conduct a thorough code review focusing on all instances where URIs are constructed or manipulated using URI.join, URI#merge, or URI#+, verifying that userinfo components are not unintentionally retained or exposed. 3. Implement logging and monitoring to detect any unusual URI patterns or potential credential leakage in application logs or network traffic. 4. Avoid embedding sensitive credentials directly in URIs; use alternative secure authentication mechanisms such as headers or tokens. 5. Educate developers on secure URI handling practices and the risks of retaining sensitive information in URI components. 6. For legacy systems where immediate upgrade is not feasible, consider applying code-level patches or wrappers that explicitly clear userinfo fields after URI manipulations. 7. Review and update security policies to include checks for sensitive data leakage in URI handling during development and security assessments.

Description

In the URI gem before 1.0.3 for Ruby, the URI handling methods (URI.join, URI#merge, URI#+) have an inadvertent leakage of authentication credentials because userinfo is retained even after changing the host.

Impact

For European organizations, the primary impact of CVE-2025-27221 is the potential leakage of authentication credentials embedded in URIs during manipulation. This can lead to unauthorized disclosure of sensitive information, which may facilitate further attacks such as unauthorized access or credential theft. Although the vulnerability does not directly compromise system integrity or availability, the confidentiality breach could undermine trust, lead to compliance violations (e.g., GDPR), and expose organizations to reputational damage. Organizations relying on Ruby-based web applications, APIs, or microservices that use the affected URI gem versions are at risk, especially if they handle sensitive user credentials or internal authentication tokens within URIs. The low CVSS score and lack of known exploits suggest a limited immediate threat, but the risk increases if attackers discover ways to exploit this leakage in complex attack chains. European sectors with stringent data protection requirements, such as finance, healthcare, and government, should prioritize addressing this vulnerability to maintain compliance and secure sensitive data flows.

CWE-212Improper Removal of Sensitive Information Before Storage or Transfer (opens in a new tab)
Base weakness
The product stores, transfers, or shares a resource that contains sensitive information, but it does not properly remove that information before the product makes the resource available to unauthorized actors.
Requirements
Clearly specify which information should be regarded as private or sensitive, and require that the product offers functionality that allows the user to cleanse the sensitive information from the resource before it is published or exported to other parties.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
Implementation · Operation · Attack Surface Reduction
Some tools can automatically analyze documents to redact, strip, or "sanitize" private information, although some human review might be necessary. Tools may vary in terms of which document formats can be processed.
OWASP ASVS 4.0.3
V8.3.2 (opens in a new tab)
Attack patterns
Windows ::DATA Alternate Data Stream (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Nov 2025, 20:59 UTC

WeaknessesCWE-212

Technical details

References

Community reviews

Related threats