<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 29 Sep 2026 15:47:41 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-33637 — Faraday: Protocol-relative URI objects still bypass host scoping (possible incomplete fix for GHSA-33mh-2634-fwr2)</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-33637</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; lostisland faraday&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; lostisland faraday&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-33637</guid>
    </item>
    <item>
      <title>GHSA-5rv5-xj5j-3484 — Faraday has a possible incomplete fix for GHSA-33mh-2634-fwr2: protocol-relative URI objects still bypass host scoping</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-5rv5-xj5j-3484</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; RubyGems: faraday&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;`Faraday::Connection#build_exclusive_url` still allows protocol-relative host override when the request target is provided as a `URI` object instead of a `String`. This bypasses the February 2026 fix for `GHSA-33mh-2634-fwr2` and can redirect a request built from a fixed-base `Faraday::Connection` to an attacker-controlled host while preserving connection-scoped headers such as `Authorization`.&lt;/p&gt;
&lt;p&gt;## Affected Component&lt;/p&gt;
&lt;p&gt;- **Repository File(s)/Endpoint(s)**:
  - `lib/faraday/connection.rb`
  - `lib/faraday/request.rb`
  - `spec/faraday/connection_spec.rb`
  - `spec/faraday/request_spec.rb`
- **Function(s)**:
  - `Faraday::Connection#build_exclusive_url`
  - `Faraday::Connection#run_request`
  - `Faraday::Request#url`
  - `Faraday::Request#to_env`
- **Version(s) Tested**:
  - `Faraday 2.14.1`
  - repository HEAD `a01039c948d3e9e41e03d152aed7244f0fb4d5ca`&lt;/p&gt;
&lt;p&gt;## Attacker Profile&lt;/p&gt;
&lt;p&gt;- **Who**: A remote user who can influence a per-request target/path in an application that uses a fixed-base Faraday connection
- **Access Required**: Ability to supply data that the application converts to `URI.parse(...)` and passes to `conn.get(...)`, `[conn.post](http://conn.post/)(...)`, or `req.url(...)`
- **Capability**: Control over a protocol-relative URI such as `URI(&amp;#34;//evil.example/pwn&amp;#34;)`&lt;/p&gt;
&lt;p&gt;## Steps to Reproduce&lt;/p&gt;
&lt;p&gt;1. Use the current repository checkout and load Faraday from `lib/`.
2. Build a fixed-base connection and provide a protocol-relative `URI` object to `req.url`.
3. Observe th…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; RubyGems: faraday&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;`Faraday::Connection#build_exclusive_url` still allows protocol-relative host override when the request target is provided as a `URI` object instead of a `String`. This bypasses the February 2026 fix for `GHSA-33mh-2634-fwr2` and can redirect a request built from a fixed-base `Faraday::Connection` to an attacker-controlled host while preserving connection-scoped headers such as `Authorization`.&lt;/p&gt;
&lt;p&gt;## Affected Component&lt;/p&gt;
&lt;p&gt;- **Repository File(s)/Endpoint(s)**:
  - `lib/faraday/connection.rb`
  - `lib/faraday/request.rb`
  - `spec/faraday/connection_spec.rb`
  - `spec/faraday/request_spec.rb`
- **Function(s)**:
  - `Faraday::Connection#build_exclusive_url`
  - `Faraday::Connection#run_request`
  - `Faraday::Request#url`
  - `Faraday::Request#to_env`
- **Version(s) Tested**:
  - `Faraday 2.14.1`
  - repository HEAD `a01039c948d3e9e41e03d152aed7244f0fb4d5ca`&lt;/p&gt;
&lt;p&gt;## Attacker Profile&lt;/p&gt;
&lt;p&gt;- **Who**: A remote user who can influence a per-request target/path in an application that uses a fixed-base Faraday connection
- **Access Required**: Ability to supply data that the application converts to `URI.parse(...)` and passes to `conn.get(...)`, `[conn.post](http://conn.post/)(...)`, or `req.url(...)`
- **Capability**: Control over a protocol-relative URI such as `URI(&amp;#34;//evil.example/pwn&amp;#34;)`&lt;/p&gt;
&lt;p&gt;## Steps to Reproduce&lt;/p&gt;
&lt;p&gt;1. Use the current repository checkout and load Faraday from `lib/`.
2. Build a fixed-base connection and provide a protocol-relative `URI` object to `req.url`.
3. Observe th…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-5rv5-xj5j-3484</guid>
    </item>
  </channel>
</rss>
