<?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>Mon, 28 Sep 2026 13:14:03 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-94301 — Apache MINA: CVE-2026-47065 resolveProxyClass fix missing from 2.0.X and 2.1.X branches (2.0.30 / 2.1.14) ZDRES-232</title>
      <link>https://db.gcve.eu/vuln/cve-2026-94301</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Apache Software Foundation Apache MINA&lt;/p&gt;
&lt;p&gt;The fix for CVE-2026-47065/ZDRES-232 (&amp;#34;resolveProxyClass Not Overridden - acceptMatchers Filter Bypass via java.lang.reflect.Proxy&amp;#34;), released on 2026-06-02 and announced as &amp;#34;Fully addressed&amp;#34; in MINA 2.2.8, 2.1.13 and 2.0.29, was committed to the
 2.2.X branch only. The 2.0.X and 2.1.X maintenance branches never received the resolveProxyClass() override, so the 2.0.29 and 2.1.13 artifacts listed as fixed -- and every later release on those lines, up to and including the current 2.0.30 and 2.1.14 -- remain vulnerable to the exact allow-list bypass that CVE-2026-47065 was meant to close.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Apache Software Foundation Apache MINA&lt;/p&gt;
&lt;p&gt;The fix for CVE-2026-47065/ZDRES-232 (&amp;#34;resolveProxyClass Not Overridden - acceptMatchers Filter Bypass via java.lang.reflect.Proxy&amp;#34;), released on 2026-06-02 and announced as &amp;#34;Fully addressed&amp;#34; in MINA 2.2.8, 2.1.13 and 2.0.29, was committed to the
 2.2.X branch only. The 2.0.X and 2.1.X maintenance branches never received the resolveProxyClass() override, so the 2.0.29 and 2.1.13 artifacts listed as fixed -- and every later release on those lines, up to and including the current 2.0.30 and 2.1.14 -- remain vulnerable to the exact allow-list bypass that CVE-2026-47065 was meant to close.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-94301</guid>
    </item>
  </channel>
</rss>
