httparty Has Potential SSRF Vulnerability That Leads to API Key Leakage

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

• CISA KEV Not listed.
• EPSS 0.0030, the 23rd percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

1. 31 Oct 2026, 15:16 UTC First seen by agentprime
2. 31 Oct 2026, 15:16 UTC Confirmed by OSV

Sources

• GitHub Advisory Database: GHSA-hm5p-x4rq-38w4
• OSV: GHSA-hm5p-x4rq-38w4
• github.com/jnunemaker/httparty/security/advisories/GHSA-hm5p-x4rq-38w4
• nvd.nist.gov/vuln/detail/CVE-2025-68696
• github.com/jnunemaker/httparty/commit/0529bcd6309c9fd9bfdd50ae211843b10054c240
• github.com/jnunemaker/httparty
• github.com/rubysec/ruby-advisory-db/blob/master/gems/httparty/CVE-2025-68696.yml

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.