<?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>Thu, 01 Oct 2026 14:56:35 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-23903 — Apache Shiro: Auth bypass when accessing static files only on case-insensitive filesystems</title>
      <link>https://db.gcve.eu/vuln/cve-2026-23903</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Apache Software Foundation Apache Shiro&lt;/p&gt;
&lt;p&gt;Authentication Bypass by Alternate Name vulnerability in Apache Shiro.&lt;/p&gt;
&lt;p&gt;This issue affects Apache Shiro: before 2.0.7.&lt;/p&gt;
&lt;p&gt;Users are recommended to upgrade to version 2.0.7, which fixes the issue.&lt;/p&gt;
&lt;p&gt;The issue only effects static files. If static files are served from a case-insensitive filesystem,
such as default macOS setup, static files may be accessed by varying the case of the filename in the request.
If only lower-case (common default) filters are present in Shiro, they may be bypassed this way.&lt;/p&gt;
&lt;p&gt;Shiro 2.1.0 and later has a new parameters to remediate this issue
shiro.ini: filterChainResolver.caseInsensitive = true
application.properties: shiro.caseInsensitive=true&lt;/p&gt;
&lt;p&gt;Shiro 3.0.0 and later makes this the default in shiro.ini-based configurations.
Shiro 3.0.1 and later makes this the default in all configurations, including programmatic and Spring / Spring Boot.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Apache Software Foundation Apache Shiro&lt;/p&gt;
&lt;p&gt;Authentication Bypass by Alternate Name vulnerability in Apache Shiro.&lt;/p&gt;
&lt;p&gt;This issue affects Apache Shiro: before 2.0.7.&lt;/p&gt;
&lt;p&gt;Users are recommended to upgrade to version 2.0.7, which fixes the issue.&lt;/p&gt;
&lt;p&gt;The issue only effects static files. If static files are served from a case-insensitive filesystem,
such as default macOS setup, static files may be accessed by varying the case of the filename in the request.
If only lower-case (common default) filters are present in Shiro, they may be bypassed this way.&lt;/p&gt;
&lt;p&gt;Shiro 2.1.0 and later has a new parameters to remediate this issue
shiro.ini: filterChainResolver.caseInsensitive = true
application.properties: shiro.caseInsensitive=true&lt;/p&gt;
&lt;p&gt;Shiro 3.0.0 and later makes this the default in shiro.ini-based configurations.
Shiro 3.0.1 and later makes this the default in all configurations, including programmatic and Spring / Spring Boot.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-23903</guid>
    </item>
  </channel>
</rss>
