<?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>Sat, 31 Oct 2026 22:14:31 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-114230 — Apache Qpid Proton C: Potential authentication bypass: regular AMQP frames can be sent as SASL frames</title>
      <link>https://db.gcve.eu/vuln/cve-2026-114230</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Apache Software Foundation Apache Qpid Proton C&lt;/p&gt;
&lt;p&gt;When dispatching SASL frames to authenticate the peer, Proton will also dispatch AMQP frames if they claim to be SASL frames. This allows authentication bypass. However there will be no user name set so the effects depend on how the application deals with this condition - which otherwise means that authentication has not completed yet.&lt;/p&gt;
&lt;p&gt;This issue affects Apache Qpid Proton C: through 0.40.0.&lt;/p&gt;
&lt;p&gt;Users are recommended to upgrade to version 0.41.1, which fixes the issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Apache Software Foundation Apache Qpid Proton C&lt;/p&gt;
&lt;p&gt;When dispatching SASL frames to authenticate the peer, Proton will also dispatch AMQP frames if they claim to be SASL frames. This allows authentication bypass. However there will be no user name set so the effects depend on how the application deals with this condition - which otherwise means that authentication has not completed yet.&lt;/p&gt;
&lt;p&gt;This issue affects Apache Qpid Proton C: through 0.40.0.&lt;/p&gt;
&lt;p&gt;Users are recommended to upgrade to version 0.41.1, which fixes the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-114230</guid>
    </item>
  </channel>
</rss>
