<?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://cve.radiocsirt.org</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, 06 Oct 2026 13:17:57 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-342334</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-342334</link>
      <description>EUVD-2026-342334</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-342334</guid>
    </item>
    <item>
      <title>fkie_cve-2026-54603</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-54603</link>
      <description>&lt;p&gt;OAuth2 is a Ruby wrapper for the OAuth 2.0 and 2.1 authorization frameworks, including OpenID Connect (OIDC). From 0.4.0 to 2.0.21, a protocol-relative redirect Location returned to OAuth2::Client#request overrides the request authority, so the bearer Authorization header is sent to an attacker-controlled host, leaking the credential. This issue is fixed in version 2.0.22.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;OAuth2 is a Ruby wrapper for the OAuth 2.0 and 2.1 authorization frameworks, including OpenID Connect (OIDC). From 0.4.0 to 2.0.21, a protocol-relative redirect Location returned to OAuth2::Client#request overrides the request authority, so the bearer Authorization header is sent to an attacker-controlled host, leaking the credential. This issue is fixed in version 2.0.22.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-54603</guid>
    </item>
    <item>
      <title>GHSA-pp92-crg2-gfv9 — OAuth2::Client#request: Protocol-relative redirect Location overrides authority, leaking bearer Authorization to attack…</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-pp92-crg2-gfv9</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; RubyGems: oauth2&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;When an application uses `OAuth2::Client` (typically via an `OAuth2::AccessToken`) and the configured authorization server returns a redirect whose `Location` header is a protocol-relative URI of the form `//attacker.example/leak`, `OAuth2::Client#request` resolves the redirect with `response.response.env.url.merge(location)`. Per RFC 3986 §5.2, an input that starts with `//` is a network-path reference and replaces the authority of the base URL: `URI(&amp;#34;http://idp.trusted/userinfo&amp;#34;).merge(&amp;#34;//attacker.example/leak&amp;#34;)` returns `http://attacker.example/leak`. The recursive `request(verb, full_location, req_opts)` call then re-sends the request to the attacker host while preserving the `Authorization: Bearer &amp;lt;access-token&amp;gt;` header that `OAuth2::AccessToken#configure_authentication!` installed on `req_opts[:headers]` for the original request.&lt;/p&gt;
&lt;p&gt;The result is a one-shot cross-origin credential disclosure: any 30x response from the IdP that an attacker can influence (a compromised endpoint, a tenant-controlled IdP in a multi-tenant deployment, or an open-redirect handler that does not normalise the `Location` it emits) can extract the bearer access token of the calling user.&lt;/p&gt;
&lt;p&gt;## Affected&lt;/p&gt;
&lt;p&gt;- `oauth2` v2.0.21 and all prior versions back to and including v0.4.0.
  - The underlying unsafe redirect-following behavior that reuses headers starts in v0.4.0 via https://github.com/ruby-oauth/oauth2/commit/b944da54cd70487c06d7252b9e4e7948eae56e73
  - The vulnerability was retained wh…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; RubyGems: oauth2&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;When an application uses `OAuth2::Client` (typically via an `OAuth2::AccessToken`) and the configured authorization server returns a redirect whose `Location` header is a protocol-relative URI of the form `//attacker.example/leak`, `OAuth2::Client#request` resolves the redirect with `response.response.env.url.merge(location)`. Per RFC 3986 §5.2, an input that starts with `//` is a network-path reference and replaces the authority of the base URL: `URI(&amp;#34;http://idp.trusted/userinfo&amp;#34;).merge(&amp;#34;//attacker.example/leak&amp;#34;)` returns `http://attacker.example/leak`. The recursive `request(verb, full_location, req_opts)` call then re-sends the request to the attacker host while preserving the `Authorization: Bearer &amp;lt;access-token&amp;gt;` header that `OAuth2::AccessToken#configure_authentication!` installed on `req_opts[:headers]` for the original request.&lt;/p&gt;
&lt;p&gt;The result is a one-shot cross-origin credential disclosure: any 30x response from the IdP that an attacker can influence (a compromised endpoint, a tenant-controlled IdP in a multi-tenant deployment, or an open-redirect handler that does not normalise the `Location` it emits) can extract the bearer access token of the calling user.&lt;/p&gt;
&lt;p&gt;## Affected&lt;/p&gt;
&lt;p&gt;- `oauth2` v2.0.21 and all prior versions back to and including v0.4.0.
  - The underlying unsafe redirect-following behavior that reuses headers starts in v0.4.0 via https://github.com/ruby-oauth/oauth2/commit/b944da54cd70487c06d7252b9e4e7948eae56e73
  - The vulnerability was retained wh…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-pp92-crg2-gfv9</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-54603</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-54603</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: ruby-oauth2, Ubuntu:18.04:LTS: ruby-oauth2, Ubuntu:20.04:LTS: ruby-oauth2, Ubuntu:22.04:LTS: ruby-oauth2, Ubuntu:24.04:LTS: ruby-oauth2, Ubuntu:26.04:LTS: ruby-oauth2&lt;/p&gt;
&lt;p&gt;OAuth2 is a Ruby wrapper for the OAuth 2.0 and 2.1 authorization frameworks, including OpenID Connect (OIDC). From 0.4.0 to 2.0.21, a protocol-relative redirect Location returned to OAuth2::Client#request overrides the request authority, so the bearer Authorization header is sent to an attacker-controlled host, leaking the credential. This issue is fixed in version 2.0.22.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: ruby-oauth2, Ubuntu:18.04:LTS: ruby-oauth2, Ubuntu:20.04:LTS: ruby-oauth2, Ubuntu:22.04:LTS: ruby-oauth2, Ubuntu:24.04:LTS: ruby-oauth2, Ubuntu:26.04:LTS: ruby-oauth2&lt;/p&gt;
&lt;p&gt;OAuth2 is a Ruby wrapper for the OAuth 2.0 and 2.1 authorization frameworks, including OpenID Connect (OIDC). From 0.4.0 to 2.0.21, a protocol-relative redirect Location returned to OAuth2::Client#request overrides the request authority, so the bearer Authorization header is sent to an attacker-controlled host, leaking the credential. This issue is fixed in version 2.0.22.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-54603</guid>
    </item>
  </channel>
</rss>
