VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

faraday: vulnerability history, versions and safety

faraday is a package in the RubyGems ecosystem. Vulert records 3 vulnerabilities for it across 117 releases, from Feb 2026 to Jun 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded H1 M1 L1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
3 in the last 12 months

Most recent disclosure 19 Jun 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all faraday vulnerabilities

Vulert verdict on faraday 2.15.0 i

Updated on 23 Oct 2026

Good news: 2.15.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 3.

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

What to do: Stay on 2.15.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 2.15.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 2.15.0 — unaffected i
  • Vulnerabilities on record 3 over 1 year · 3 in the last year i
  • Latest disclosure 19 Jun 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Stars 5,951 i
  • OpenSSF scorecard 4/10 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by RubyGems, refreshed 23 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 faraday, 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
2.15.0 16 Oct 2026 none MIT — Details →
2.14.4 15 Sep 2026 none MIT — Details →
1.10.6 24 Jun 2026 H1 M1 MIT Yes Details →
2.14.3 16 Jun 2026 none MIT — Details →
2.14.2 15 May 2026 H1 MIT Yes Details →
1.10.5 12 Feb 2026 H1 MIT Yes Details →
2.14.1 07 Feb 2026 H1 L1 MIT Yes Details →
2.14.0 28 Sep 2025 H1 M1 L1 MIT Yes Details →
2.13.4 25 Jul 2025 H1 M1 L1 MIT Yes Details →
2.13.3 22 Jul 2025 H1 M1 L1 MIT Yes Details →
2.13.2 04 Jul 2025 H1 M1 L1 MIT Yes Details →
2.13.1 25 Apr 2025 H1 M1 L1 MIT Yes Details →
2.13.0 08 Apr 2025 H1 M1 L1 MIT Yes Details →
2.12.3 08 Apr 2025 H1 M1 L1 MIT Yes Details →
2.12.2 09 Dec 2024 H1 M1 L1 MIT Yes Details →
2.12.1 14 Nov 2024 H1 M1 L1 MIT Yes Details →
1.10.4 20 Sep 2024 H1 M1 MIT Yes Details →
2.12.0 18 Sep 2024 H1 M1 L1 MIT Yes Details →
2.11.0 26 Aug 2024 H1 M1 L1 MIT Yes Details →
2.10.1 31 Jul 2024 H1 M1 L1 MIT Yes Details →
2.10.0 08 Jul 2024 H1 M1 L1 MIT Yes Details →
2.9.2 18 Jun 2024 H1 M1 L1 MIT Yes Details →
2.9.1 05 Jun 2024 H1 M1 L1 MIT Yes Details →
2.9.0 09 Jan 2024 H1 M1 L1 MIT Yes Details →
2.8.1 21 Dec 2023 H1 M1 L1 MIT Yes Details →
2.8.0 20 Dec 2023 H1 M1 L1 MIT Yes Details →
2.7.12 21 Nov 2023 H1 M1 L1 MIT Yes Details →
2.7.11 12 Sep 2023 H1 M1 L1 MIT Yes Details →
2.7.10 06 Jul 2023 H1 M1 L1 MIT Yes Details →
2.7.9 30 Jun 2023 H1 M1 L1 MIT Yes Details →
2.7.8 28 Jun 2023 H1 M1 L1 MIT Yes Details →
2.7.7 20 Jun 2023 H1 M1 L1 MIT Yes Details →
2.7.6 07 Jun 2023 H1 M1 L1 MIT Yes Details →
2.7.5 23 May 2023 H1 M1 L1 MIT Yes Details →
2.7.4 20 Jan 2023 H1 M1 L1 MIT Yes Details →
1.10.3 18 Jan 2023 H1 M1 MIT Yes Details →
2.7.3 16 Jan 2023 H1 M1 L1 MIT Yes Details →
2.7.2 14 Dec 2022 H1 M1 L1 MIT Yes Details →
2.7.1 18 Nov 2022 H1 M1 L1 MIT Yes Details →
2.7.0 15 Nov 2022 H1 M1 L1 MIT Yes Details →
0.17.6 04 Nov 2022 H1 M1 MIT Yes Details →
2.6.0 03 Oct 2022 H1 M1 L1 MIT Yes Details →
1.10.2 23 Aug 2022 H1 M1 MIT Yes Details →
2.5.2 11 Aug 2022 H1 M1 L1 MIT Yes Details →
2.5.1 08 Aug 2022 H1 M1 L1 MIT Yes Details →
2.5.0 08 Aug 2022 H1 M1 L1 MIT Yes Details →
1.10.1 08 Aug 2022 H1 M1 MIT Yes Details →
2.4.0 28 Jul 2022 H1 M1 L1 MIT Yes Details →
2.3.0 06 May 2022 H1 M1 L1 MIT Yes Details →
0.17.5 21 Feb 2022 H1 M1 MIT Yes Details →
1.10.0 17 Feb 2022 H1 M1 MIT Yes Details →
2.2.0 03 Feb 2022 H1 M1 L1 MIT Yes Details →
2.1.0 15 Jan 2022 H1 M1 L1 MIT Yes Details →
1.9.3 06 Jan 2022 H1 M1 MIT Yes Details →
1.9.2 06 Jan 2022 H1 M1 MIT Yes Details →
1.9.1 06 Jan 2022 H1 M1 MIT Yes Details →
1.9.0 06 Jan 2022 H1 M1 MIT Yes Details →
2.0.1 05 Jan 2022 H1 M1 L1 MIT Yes Details →
2.0.0 04 Jan 2022 H1 M1 L1 MIT Yes Details →
2.0.0.alpha.pre.4 15 Dec 2021 H1 M1 MIT Yes Details →
2.0.0.alpha.pre.3 30 Nov 2021 H1 M1 MIT Yes Details →
2.0.0.alpha.pre.2 28 Oct 2021 H1 M1 MIT Yes Details →
2.0.0.alpha.pre.1 25 Oct 2021 H1 M1 MIT Yes Details →
1.8.0 18 Sep 2021 H1 M1 MIT Yes Details →
1.7.2 13 Sep 2021 H1 M1 MIT Yes Details →
1.7.1 30 Aug 2021 H1 M1 MIT Yes Details →
1.7.0 09 Aug 2021 H1 M1 MIT Yes Details →
1.6.0 01 Aug 2021 H1 M1 MIT Yes Details →
1.5.1 11 Jul 2021 H1 M1 MIT Yes Details →
1.5.0 04 Jul 2021 H1 M1 MIT Yes Details →
1.4.3 24 Jun 2021 H1 M1 MIT Yes Details →
1.4.2 22 May 2021 H1 M1 MIT Yes Details →
1.4.1 18 Apr 2021 H1 M1 MIT Yes Details →
1.4.0 16 Apr 2021 H1 M1 MIT Yes Details →
1.3.1 16 Apr 2021 H1 M1 MIT Yes Details →
0.17.4 06 Feb 2021 H1 M1 MIT Yes Details →
1.3.0 31 Dec 2020 H1 M1 MIT Yes Details →
1.2.0 23 Dec 2020 H1 M1 MIT Yes Details →
1.1.0 17 Oct 2020 H1 M1 MIT Yes Details →
1.0.1 29 Mar 2020 H1 M1 MIT Yes Details →
1.0.0 01 Jan 2020 H1 M1 MIT Yes Details →
0.17.3 31 Dec 2019 H1 M1 MIT Yes Details →
0.17.1 27 Nov 2019 H1 M1 MIT Yes Details →
0.17.0 06 Oct 2019 H1 M1 MIT Yes Details →
0.16.2 29 Sep 2019 H1 M1 MIT Yes Details →
0.16.1 27 Sep 2019 H1 M1 MIT Yes Details →
0.16.0 27 Sep 2019 H1 M1 MIT Yes Details →
1.0.0.pre.rc1 08 Jul 2019 H1 M1 MIT Yes Details →
0.15.4 27 Nov 2018 H1 M1 MIT Yes Details →
0.15.3 19 Sep 2018 H1 M1 MIT Yes Details →
0.15.2 23 May 2018 H1 M1 MIT Yes Details →
0.15.1 10 May 2018 H1 M1 MIT Yes Details →
0.15.0 19 Apr 2018 H1 M1 MIT Yes Details →
0.14.0 19 Jan 2018 H1 M1 MIT Yes Details →
0.13.1 18 Aug 2017 H1 M1 MIT Yes Details →
0.13.0 15 Aug 2017 H1 M1 MIT Yes Details →
0.12.2 21 Jul 2017 H1 M1 MIT Yes Details →
0.12.1 21 Apr 2017 H1 M1 MIT Yes Details →
0.12.0.1 02 Apr 2017 H1 M1 MIT Yes Details →
0.12.0 01 Apr 2017 H1 M1 MIT Yes Details →
0.11.0 13 Jan 2017 H1 M1 — Yes Details →
0.10.1 30 Dec 2016 H1 M1 — Yes Details →
0.10.0 11 Nov 2016 H1 M1 — Yes Details →
0.8.11 07 Oct 2015 H1 M1 — Yes Details →
0.9.2 06 Oct 2015 H1 M1 — Yes Details →
0.8.10 21 Aug 2015 H1 M1 — Yes Details →
0.9.1 07 Jan 2015 H1 M1 — Yes Details →
0.9.0 16 Jan 2014 H1 M1 — Yes Details →
0.9.0.rc7 10 Jan 2014 H1 M1 — Yes Details →
0.8.9 10 Jan 2014 H1 M1 — Yes Details →
0.9.0.rc6 09 Nov 2013 H1 M1 — Yes Details →
0.8.8 26 Jul 2013 H1 M1 — Yes Details →
0.9.0.rc5 13 May 2013 H1 M1 — Yes Details →
0.9.0.rc4 13 May 2013 H1 M1 — Yes Details →
0.9.0.rc3 13 May 2013 H1 M1 — Yes Details →
0.9.0.rc2 13 May 2013 H1 M1 — Yes Details →
0.9.0.rc1 08 May 2013 H1 M1 — Yes Details →
0.8.7 24 Mar 2013 H1 M1 — Yes Details →
0.8.6 25 Feb 2013 H1 M1 — Yes Details →
0.8.5 04 Feb 2013 H1 M1 — Yes Details →

The newest 120 of 162 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 3

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

03 Vulnerabilities

Recorded vulnerabilities for faraday

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Faraday: Uncontrolled recursion in NestedParamsEncoder allows stack exhaustion DoS via deeply nested... 7.5 high 2.14.3 19 Jun 2026
CVE-2026-25765: Faraday SSRF Vulnerability via Protocol-Relative URL Host Override 5.8 medium 2.14.1 09 Feb 2026
CVE-2026-33637: Faraday Incomplete Fix Allows Protocol-Relative URI Bypass 0.0 low 2.14.2 18 May 2026

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 faraday

Is faraday safe to use?

Vulert records 3 vulnerabilities for faraday in RubyGems: 0 critical, 1 high, 1 medium and 1 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is faraday's Vulert package health score?

Vulert scores faraday 78/100, which reads as in good shape. 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).

Is the latest version of faraday affected?

No. 2.15.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

How many vulnerabilities does faraday have?

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

How often are new faraday vulnerabilities disclosed?

3 vulnerabilities were recorded for faraday in the last 12 months, and the oldest entry in this database dates to 09 Feb 2026. 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 faraday 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 faraday for upcoming vulnerabilities?

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