<?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>Wed, 07 Oct 2026 12:21:37 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-362494</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-362494</link>
      <description>EUVD-2026-362494</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-362494</guid>
    </item>
    <item>
      <title>fkie_cve-2026-81888</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-81888</link>
      <description>&lt;p&gt;@hono/oauth-providers is Authentication middleware for Hono. Prior to version 0.8.6, the built-in social login providers accept an OAuth callback even when the `state` value is absent on both sides, so the anti-CSRF check passes for a callback that never came from a genuine login attempt. This defeats the `state`-based CSRF protection under default usage. Version 0.8.6 has a patch.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;@hono/oauth-providers is Authentication middleware for Hono. Prior to version 0.8.6, the built-in social login providers accept an OAuth callback even when the `state` value is absent on both sides, so the anti-CSRF check passes for a callback that never came from a genuine login attempt. This defeats the `state`-based CSRF protection under default usage. Version 0.8.6 has a patch.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-81888</guid>
    </item>
    <item>
      <title>GHSA-fm3f-ch8h-qw8q — @hono/oauth-providers: OAuth state check fails open on omitted state, enabling login CSRF and forced account linking</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-fm3f-ch8h-qw8q</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @hono/oauth-providers&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;The built-in social login providers accept an OAuth callback even when the `state` value is absent on both sides, so the anti-CSRF check passes for a callback that never came from a genuine login attempt. This defeats the `state`-based CSRF protection under default usage.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;The `state` check treated two absent values as a match, so a callback that omits `state` — and for which no `state` was ever stored — was allowed to redeem the authorization code. Hono&amp;#39;s `csrf()` middleware does not help: it only inspects form-style requests, while the OAuth callback is a top-level `GET` navigation it treats as safe.&lt;/p&gt;
&lt;p&gt;This affects the `google`, `github`, `facebook`, `discord`, `twitch`, `linkedin`, and `msentra` providers. The `x` (Twitter) provider is not exploitable due to its PKCE binding.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;An attacker can make a victim&amp;#39;s browser complete an OAuth callback that binds the attacker&amp;#39;s identity instead of the victim&amp;#39;s, leading to login CSRF (the victim silently acts inside the attacker&amp;#39;s account) or forced account linking (the attacker&amp;#39;s identity is linked to the victim&amp;#39;s account, enabling later sign-in as the victim). Affects applications using an affected provider on `@hono/oauth-providers` `0.8.5` or earlier.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @hono/oauth-providers&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;The built-in social login providers accept an OAuth callback even when the `state` value is absent on both sides, so the anti-CSRF check passes for a callback that never came from a genuine login attempt. This defeats the `state`-based CSRF protection under default usage.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;The `state` check treated two absent values as a match, so a callback that omits `state` — and for which no `state` was ever stored — was allowed to redeem the authorization code. Hono&amp;#39;s `csrf()` middleware does not help: it only inspects form-style requests, while the OAuth callback is a top-level `GET` navigation it treats as safe.&lt;/p&gt;
&lt;p&gt;This affects the `google`, `github`, `facebook`, `discord`, `twitch`, `linkedin`, and `msentra` providers. The `x` (Twitter) provider is not exploitable due to its PKCE binding.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;An attacker can make a victim&amp;#39;s browser complete an OAuth callback that binds the attacker&amp;#39;s identity instead of the victim&amp;#39;s, leading to login CSRF (the victim silently acts inside the attacker&amp;#39;s account) or forced account linking (the attacker&amp;#39;s identity is linked to the victim&amp;#39;s account, enabling later sign-in as the victim). Affects applications using an affected provider on `@hono/oauth-providers` `0.8.5` or earlier.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-fm3f-ch8h-qw8q</guid>
    </item>
  </channel>
</rss>
