VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

httparty: vulnerability history, versions and safety

httparty is a package in the RubyGems ecosystem. Vulert records 4 vulnerabilities for it across 88 releases, from Oct 2017 to Dec 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded H2 M2
i
2 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
1 in the last 12 months

Most recent disclosure 23 Dec 2025.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all httparty vulnerabilities

Vulert verdict on httparty 0.24.3 i

Updated on 23 Oct 2026

Careful: 0.24.3 has 2 known vulnerabilities, and 2 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Quiet

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 0.24.3 — affected i
  • Vulnerabilities on record 4 over 8 years · 1 in the last year i
  • Latest disclosure 23 Dec 2025 i
  • Highest CVSS 7.8 i
  • With no published fix 2 i
  • Stars 5,899 i
  • OpenSSF scorecard 2/10 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by RubyGems, refreshed 22 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for httparty, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
0.24.3 30 Sep 2026 H1 M1 MIT No Details →
0.24.2 14 Jan 2026 H1 M1 MIT No Details →
0.24.1 14 Jan 2026 H1 M1 MIT No Details →
0.24.0 28 Dec 2025 H1 M1 MIT No Details →
0.23.2 07 Oct 2025 H1 MIT No Details →
0.23.1 28 Mar 2025 H1 MIT No Details →
0.23.0 27 Mar 2025 H1 MIT No Details →
0.22.0 29 Apr 2024 H1 MIT No Details →
0.21.0 30 Dec 2022 H1 MIT No Details →
0.20.0 29 Sep 2021 H1 M2 MIT No Details →
0.19.1 29 Sep 2021 H1 M2 MIT No Details →
0.19.0 09 Sep 2021 H1 M2 MIT No Details →
0.18.1 10 Jun 2020 H1 M2 MIT No Details →
0.18.0 19 Feb 2020 H1 M2 MIT No Details →
0.17.3 16 Dec 2019 H1 M2 MIT No Details →
0.17.1 18 Sep 2019 H1 M2 MIT No Details →
0.17.0 20 Apr 2019 H1 M2 MIT No Details →
0.16.4 05 Feb 2019 H1 M2 MIT No Details →
0.16.3 12 Nov 2018 H1 M2 MIT No Details →
0.16.2 30 Mar 2018 H1 M2 MIT No Details →
0.16.1 12 Mar 2018 H1 M2 MIT No Details →
0.16.0 13 Feb 2018 H1 M2 MIT No Details →
0.15.7 07 Feb 2018 H1 M2 MIT No Details →
0.15.6 21 Jul 2017 H1 M2 MIT No Details →
0.15.5 19 May 2017 H1 M2 MIT No Details →
0.15.4 17 May 2017 H1 M2 MIT No Details →
0.15.3 16 May 2017 H1 M2 MIT No Details →
0.15.2 12 May 2017 H1 M2 MIT No Details →
0.15.1 12 May 2017 H1 M2 MIT No Details →
0.15.0 11 May 2017 H1 M2 MIT No Details →
0.14.0 25 Jul 2016 H1 M2 MIT No Details →
0.13.7 23 Sep 2015 H1 M2 MIT No Details →
0.13.6 21 Sep 2015 H1 M2 MIT No Details →
0.13.5 19 May 2015 H1 M2 MIT No Details →
0.13.4 13 May 2015 H1 M2 MIT No Details →
0.13.3 06 Nov 2014 H1 M2 MIT No Details →
0.13.2 03 Nov 2014 H1 M2 MIT No Details →
0.13.1 08 Apr 2014 H1 M2 — No Details →
0.13.0 14 Feb 2014 H1 M2 — No Details →
0.12.0 10 Oct 2013 H1 M2 — No Details →
0.11.0 10 Apr 2013 H1 M2 — No Details →
0.10.2 27 Jan 2013 H1 M2 — No Details →
0.10.1 26 Jan 2013 H1 M2 — No Details →
0.10.0 10 Jan 2013 H1 M2 — No Details →
0.9.0 07 Sep 2012 H2 M2 — No Details →
0.8.3 22 Apr 2012 H2 M2 — No Details →
0.8.2 12 Apr 2012 H2 M2 — No Details →
0.8.1 05 Oct 2011 H2 M2 — No Details →
0.8.0 13 Sep 2011 H2 M2 — No Details →
0.7.8 07 Jun 2011 H2 M2 — No Details →
0.7.7 20 Apr 2011 H2 M2 — No Details →
0.7.6 16 Apr 2011 H2 M2 — No Details →
0.7.4 13 Feb 2011 H2 M2 — No Details →
0.7.3 20 Jan 2011 H2 M2 — No Details →
0.7.2 20 Jan 2011 H2 M2 — No Details →
0.7.0 18 Jan 2011 H2 M2 — No Details →
0.6.1 07 Jul 2010 H2 M2 — No Details →
0.6.0 13 Jun 2010 H2 M2 — No Details →
0.5.2 31 Jan 2010 H2 M2 — No Details →
0.5.1 31 Jan 2010 H2 M2 — No Details →
0.5.0 08 Dec 2009 H2 M2 — No Details →
0.4.5 24 Sep 2009 H2 M2 — No Details →
0.4.4 05 Aug 2009 H2 M2 — No Details →
0.1.0 25 Jul 2009 H2 M2 — No Details →
0.1.1 25 Jul 2009 H2 M2 — No Details →
0.1.2 25 Jul 2009 H2 M2 — No Details →
0.1.3 25 Jul 2009 H2 M2 — No Details →
0.1.5 25 Jul 2009 H2 M2 — No Details →
0.1.6 25 Jul 2009 H2 M2 — No Details →
0.1.7 25 Jul 2009 H2 M2 — No Details →
0.1.8 25 Jul 2009 H2 M2 — No Details →
0.2.0 25 Jul 2009 H2 M2 — No Details →
0.2.1 25 Jul 2009 H2 M2 — No Details →
0.2.10 25 Jul 2009 H2 M2 — No Details →
0.2.2 25 Jul 2009 H2 M2 — No Details →
0.2.3 25 Jul 2009 H2 M2 — No Details →
0.2.4 25 Jul 2009 H2 M2 — No Details →
0.2.5 25 Jul 2009 H2 M2 — No Details →
0.2.6 25 Jul 2009 H2 M2 — No Details →
0.2.7 25 Jul 2009 H2 M2 — No Details →
0.2.8 25 Jul 2009 H2 M2 — No Details →
0.2.9 25 Jul 2009 H2 M2 — No Details →
0.3.0 25 Jul 2009 H2 M2 — No Details →
0.3.1 25 Jul 2009 H2 M2 — No Details →
0.4.0 25 Jul 2009 H2 M2 — No Details →
0.4.1 25 Jul 2009 H2 M2 — No Details →
0.4.2 25 Jul 2009 H2 M2 — No Details →
0.4.3 25 Jul 2009 H2 M2 — No Details →

All 88 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2017 1
  • 2023 1
  • 2024 1
  • 2025 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 1 of the 4 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for httparty

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
SSRF Vulnerability in httparty: Risk of API Key Leakage 7.8 high No fix published 23 Dec 2025
Multipart/Form-Data Request Tampering Vulnerability in httparty 6.5 medium 0.21.0 03 Jan 2023
Duplicate Advisory: httparty has multipart/form-data request tampering vulnerability 5.3 medium No fix published 04 Jan 2024
CVE-2013-1801: HTTParty Gem Object-Injection Vulnerability N/A high 0.10.0 24 Oct 2017

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About httparty

Is httparty safe to use?

Vulert records 4 vulnerabilities for httparty in RubyGems: 0 critical, 2 high, 2 medium and 0 low. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is httparty's Vulert package health score?

Vulert scores httparty 60/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of httparty affected?

Yes. 0.24.3, the version you would install today, has 2 known vulnerabilities, and 2 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of httparty should I use?

0.24.3 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does httparty have?

4 vulnerabilities are recorded for httparty in the RubyGems ecosystem: 0 critical, 2 high, 2 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new httparty vulnerabilities disclosed?

1 vulnerability was recorded for httparty in the last 12 months, and the oldest entry in this database dates to 24 Oct 2017. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of httparty are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor httparty for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the httparty version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.