Is faraday 1.6 vulnerable?

RubyGems · 1 release from 1.6.0 to 1.6.0 · latest faraday is 2.15.1 · checked 18 Nov 2026

Yes: 2 known advisories

Yes. faraday 1.6.0, the last 1.6 release, is affected by 2 known security advisories (1 high, 1 medium), including CVE-2026-54297, CVE-2026-25765. Upgrade to 1.10.6 or later to fix all of them.

Upgrade with:bundle update --conservative faraday # Gemfile: '>= 1.10.6'

Is your project on an affected faraday?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Advisories affecting faraday 1.6.0

  • HighCVE-2026-54297GHSA-98m9-hrrm-r99r19 Jun 2026

    Faraday: Uncontrolled recursion in NestedParamsEncoder allows stack exhaustion DoS via deeply nested query parameters

    Affected
    >=2.0.0 <2.14.3 · >=1.0.0 <1.10.6
    Fixed in
    1.10.6, 2.14.3
  • MediumCVE-2026-25765GHSA-33mh-2634-fwr29 Feb 2026

    Faraday affected by SSRF via protocol-relative URL host override in build_exclusive_url

    Affected
    >=2.0.0 <2.14.1 · >=1.0.0 <1.10.5
    Fixed in
    1.10.5, 2.14.1

Which of your client projects are still on faraday 1.6?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact faraday version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other faraday versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the RubyGems registry. Refreshed daily.