CVE-2025-68696VulnerabilityPublished 23 Dec 2025

CVE-2025-68696: jnunemaker httparty · Server-Side Request Forgery (SSRF)

Affects jnunemaker httpartySource CVE Database V5

Not known to be exploited · CVSS 7.8 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

7.8High

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

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: High
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

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

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, 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: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: High: There is a total loss of confidentiality, resulting in all information within the Vulnerable System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 23 Dec 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
RubyGemshttparty`pkg:gem/httparty`Other threats	Affected <=0.23.2	Fixed in–

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

AI-suggested

European organizations should immediately upgrade all instances of httparty to versions later than 0.23.2 where the SSRF vulnerability is patched. Conduct a thorough inventory of applications and services using httparty to ensure no vulnerable versions remain in production or development environments. Implement strict input validation and sanitization on all user-supplied URLs or parameters that may be used in HTTP requests to prevent malicious request injection. Employ network segmentation and firewall rules to restrict server access to only necessary internal resources, limiting the potential impact of SSRF exploitation. Monitor outbound traffic from servers running httparty for unusual or unauthorized requests to internal or external endpoints. Use runtime application self-protection (RASP) or web application firewalls (WAFs) configured to detect and block SSRF attack patterns. Finally, review and rotate any API keys or credentials that may have been exposed or are at risk due to this vulnerability.

Description

CVE-2025-68696 is a high-severity Server-Side Request Forgery (SSRF) vulnerability affecting httparty versions 0.23.2 and earlier. This flaw allows attackers to make unauthorized requests from the vulnerable server to internal or external systems, potentially exposing sensitive data such as API keys. The vulnerability requires no authentication or user interaction and can be exploited remotely over the network. It has been patched in later versions of httparty. European organizations using vulnerable versions of httparty in their API integrations or web applications face risks of data leakage and internal network reconnaissance. No known exploits are currently reported in the wild, but the ease of exploitation and potential impact warrant immediate remediation. Organizations should upgrade to patched versions and audit internal API usage to mitigate risk. Countries with significant software development sectors and high adoption of Ruby-based tools, such as Germany, the UK, and France, are most likely to be affected.

Impact

For European organizations, this SSRF vulnerability poses a significant risk to confidentiality and internal network security. Exploitation can lead to unauthorized disclosure of API keys, which may grant attackers access to critical cloud services, databases, or third-party APIs. Additionally, attackers can use the SSRF to pivot within internal networks, potentially accessing sensitive systems that are otherwise protected by firewalls. This can result in data breaches, service disruptions, or further lateral movement by threat actors. Organizations with complex microservice architectures or internal APIs are particularly vulnerable. The vulnerability's ease of exploitation and lack of required authentication increase the likelihood of attacks, which could impact sectors such as finance, healthcare, and government services across Europe. The absence of known exploits in the wild currently reduces immediate risk but does not eliminate the threat, especially as attackers often develop exploits rapidly after public disclosure.

Summary

CVE-2025-68696 identifies a Server-Side Request Forgery (SSRF) vulnerability in the httparty library, a popular Ruby-based HTTP client used for API interactions. Versions 0.23.2 and prior are vulnerable, allowing unauthenticated attackers to craft malicious requests that the server then executes. SSRF vulnerabilities enable attackers to bypass network access controls by leveraging the server as a proxy to send requests to internal systems or external endpoints. In this case, exploitation can lead to leakage of sensitive information such as API keys embedded in requests or responses, and unauthorized access to internal services that are not directly exposed to the internet. The vulnerability does not require any privileges or user interaction, increasing its risk profile. The issue was addressed and patched in a subsequent commit (0529bcd), and users are advised to upgrade. The CVSS 4.0 base score of 7.8 reflects high severity due to network attack vector, no required privileges or user interaction, and high impact on confidentiality. While no known exploits have been reported in the wild, the vulnerability's characteristics make it a significant threat to applications relying on httparty for HTTP requests, especially in complex internal network environments.

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 31 Dec 2025, 00:28 UTC

WeaknessesCWE-918

Technical details

References

Community reviews

Related threats