Is faraday 1.7 vulnerable?
RubyGems · 3 releases from 1.7.0 to 1.7.2 · latest faraday is 2.15.1 · checked 18 Nov 2026
Yes: 2 known advisories
Yes. faraday 1.7.2, the last 1.7 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.
bundle update --conservative faraday # Gemfile: '>= 1.10.6'Is your project on an affected faraday?
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.7.2
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
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
Every faraday 1.7.x release
Affected: 1.7.0 to 1.7.2. Latest faraday: 2.15.1.
| Version | Known advisories |
|---|---|
| faraday 1.7.2 | CVE-2026-54297, CVE-2026-25765 |
| faraday 1.7.1 | CVE-2026-54297, CVE-2026-25765 |
| faraday 1.7.0 | CVE-2026-54297, CVE-2026-25765 |
Which of your client projects are still on faraday 1.7?
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.