<?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://db.gcve.eu</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 23:03:14 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-82756 — ash_authentication_oauth2_server interpolates a tenant-derived value into the WWW-Authenticate challenge without escapi…</title>
      <link>https://db.gcve.eu/vuln/cve-2026-82756</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; ash-project ash_authentication_oauth2_server&lt;/p&gt;
&lt;p&gt;Improper Encoding or Escaping of Output vulnerability in ash-project ash_authentication_oauth2_server allows an unauthenticated attacker to inject arbitrary authentication parameters into the WWW-Authenticate challenge header.&lt;/p&gt;
&lt;p&gt;BearerPlug and RequireScopePlug built the Bearer resource_metadata=&amp;#34;...&amp;#34; challenge by interpolating a resource_metadata URL derived from the request tenant directly into the quoted value. In a multi-tenant application that sets the Ash tenant from request-controlled data (a subdomain, the Host, a path segment, or a header), a tenant containing a &amp;#34; closes the quoted value and appends attacker-chosen auth-params, including a second resource_metadata URL pointing at an attacker-controlled authorization server that spec-following clients follow. Carriage returns and line feeds are rejected by Plug, so this is parameter injection within one header, not response splitting.&lt;/p&gt;
&lt;p&gt;This issue affects ash_authentication_oauth2_server: from 0.1.3 before 0.3.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; ash-project ash_authentication_oauth2_server&lt;/p&gt;
&lt;p&gt;Improper Encoding or Escaping of Output vulnerability in ash-project ash_authentication_oauth2_server allows an unauthenticated attacker to inject arbitrary authentication parameters into the WWW-Authenticate challenge header.&lt;/p&gt;
&lt;p&gt;BearerPlug and RequireScopePlug built the Bearer resource_metadata=&amp;#34;...&amp;#34; challenge by interpolating a resource_metadata URL derived from the request tenant directly into the quoted value. In a multi-tenant application that sets the Ash tenant from request-controlled data (a subdomain, the Host, a path segment, or a header), a tenant containing a &amp;#34; closes the quoted value and appends attacker-chosen auth-params, including a second resource_metadata URL pointing at an attacker-controlled authorization server that spec-following clients follow. Carriage returns and line feeds are rejected by Plug, so this is parameter injection within one header, not response splitting.&lt;/p&gt;
&lt;p&gt;This issue affects ash_authentication_oauth2_server: from 0.1.3 before 0.3.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-82756</guid>
    </item>
  </channel>
</rss>
