CVE-2026-25765VulnerabilityPublished 9 Feb 2026

CVE-2026-25765: lostisland faraday · Server-Side Request Forgery (SSRF)

Affects lostisland faradaySource CVE Database V5

Not known to be exploited · CVSS 5.8 Medium : upgrade to 2.14.1 when convenient.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score

5.8Medium

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2.14.1

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

Attack Vector: Network
Attack Complexity: Low
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: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
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 9 Feb 2026
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 26 Oct 2026.

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

Upgrade lostisland faraday to 2.14.1.

Affected software

Product	Affected	Fixed in
lostislandfaraday	Affected <2.14.1	Fixed in 2.14.1

AI-suggested

1. Upgrade all instances of the Faraday library to version 2.14.1 or later, where the vulnerability is fixed. 2. Implement strict input validation and sanitization on any user-supplied URLs or paths before passing them to Faraday request methods to prevent protocol-relative URLs or other malicious inputs. 3. Employ allowlisting of domains or IP addresses for outbound HTTP requests initiated by the application to restrict requests to trusted destinations only. 4. Use network segmentation and firewall rules to limit the vulnerable application's ability to reach sensitive internal resources or external untrusted networks. 5. Monitor application logs and network traffic for unusual outbound requests that may indicate attempted exploitation. 6. Conduct code reviews and security testing focusing on HTTP client usage patterns to identify and remediate similar SSRF risks. 7. Educate development teams about the risks of SSRF and secure handling of user input in HTTP requests. These measures combined will reduce the risk of exploitation beyond simply patching the library.

Description

CVE-2026-25765 is a Server-Side Request Forgery (SSRF) vulnerability in the lostisland Faraday HTTP client library versions prior to 2.14.1. The issue arises from the build_exclusive_url method using Ruby's URI#merge, which treats protocol-relative URLs as network-path references, allowing an attacker to override the base URL's host. If user input is passed unchecked to Faraday's request methods, an attacker can supply a protocol-relative URL to redirect requests to arbitrary hosts, potentially accessing internal resources. The vulnerability has a CVSS score of 5.8 (medium severity) and does not require authentication or user interaction. It affects applications using vulnerable Faraday versions and is fixed in version 2.14.1.

Impact

For European organizations, this SSRF vulnerability poses a risk primarily to web applications and services that utilize the Faraday HTTP client library versions prior to 2.14.1 and accept user-controlled input for HTTP requests. Exploitation could allow attackers to make arbitrary HTTP requests from the vulnerable server to internal or external systems, potentially bypassing network access controls. This may lead to unauthorized access to internal services, data exfiltration, or reconnaissance of internal network infrastructure. While the vulnerability does not directly allow data modification or denial of service, the ability to pivot within internal networks or access sensitive endpoints can have significant security implications. Organizations in sectors with sensitive data or critical infrastructure, such as finance, healthcare, and government, may face increased risks. The medium severity rating reflects the moderate impact and ease of exploitation without authentication. Given the widespread use of Ruby and Faraday in web development, European organizations using these technologies should assess their exposure and remediate promptly to prevent potential SSRF exploitation.

CWE-918Server-Side Request Forgery (SSRF) (opens in a new tab)
Base weaknessCWE Top 25 (2025): #22OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.6.1 (opens in a new tab)
V5.2.6 (opens in a new tab)
Attack patterns
Server Side Request Forgery (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 17 Feb 2026, 09:48 UTC

WeaknessesCWE-918

Technical details

References

Community reviews

Related threats