SSRF (Server-Side Request Forgery) in faraday (CVE-2026-33637)
Summary
SSRF in faraday (CVE-2026-33637). Risk of unauthorized operations or information disclosure. Exploitable via URI. Mitigation: upgrade to 2.14.2 or later.
Original description
The description as published by the source.
Faraday is an HTTP client library abstraction layer that provides a common interface over many adapters. Versions 2.0.0 through 2.14.1 still allow protocol-relative host override when the request target is passed as a URI object (rather than a String) to Faraday::Connection#build_exclusive_url. This bypasses the February 2026 fix for GHSA-33mh-2634-fwr2 and enables off-host request forgery: a request built from a fixed-base Faraday::Connection can be redirected to an attacker-controlled host, forwarding connection-scoped values such as Authorization headers and default query parameters. This issue has been fixed in version 2.14.3.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-33637 has been found in faraday.
Attackers can target a specific entry point like URI over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade faraday to 2.14.2 or later.
If unsure, ask your IT team or search "faraday CVE-2026-33637" on the vendor's site.
CVE-2026-33637 (faraday) — CWE-918
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: URI / String / Authorization / a01039c948d3e9e41e03d152aed7244f0fb4d5ca
Patched: 2.14.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
SSRF (CWE-918) exists in faraday. Attackers reach the vulnerable code path via URI without authentication.
Check the vendor advisory for the affected versions of faraday. Attack surface: URI / String / Authorization / a01039c948d3e9e41e03d152aed7244f0fb4d5ca.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2.14.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'faraday' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'faraday' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
faradayを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade faraday to 2.14.2ステージング環境で 2.14.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-33637 ruby-faraday Fixed in: 2.14.3-1
- Ubuntu UBUNTU-CVE-2026-33637 ruby-faraday
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com