<?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://vulnerability.circl.lu</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 22:22:51 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-106123</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-106123</link>
      <description>&lt;p&gt;The RabbitMQ Java client library allows Java and JVM-based applications to connect to and interact with RabbitMQ nodes. Prior to 5.35.0, ConnectionFactoryConfigurator.load() includes the raw uri value in wrapped exceptions when AMQP URI parsing fails. Because the URI may contain a plaintext username and password, startup logs, application performance monitoring systems, CI logs, and copied stack traces can disclose broker credentials to users who should not have access to them. This issue is fixed in version 5.35.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The RabbitMQ Java client library allows Java and JVM-based applications to connect to and interact with RabbitMQ nodes. Prior to 5.35.0, ConnectionFactoryConfigurator.load() includes the raw uri value in wrapped exceptions when AMQP URI parsing fails. Because the URI may contain a plaintext username and password, startup logs, application performance monitoring systems, CI logs, and copied stack traces can disclose broker credentials to users who should not have access to them. This issue is fixed in version 5.35.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-106123</guid>
    </item>
    <item>
      <title>GHSA-h6w7-qmcm-q6xr — RabbitMQ Java client: plaintext broker credentials leaked in exception message from ConnectionFactoryConfigurator.load()</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-h6w7-qmcm-q6xr</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: com.rabbitmq:amqp-client&lt;/p&gt;
&lt;p&gt;### Summary
When property-file/Map-based `ConnectionFactory` setup fails while parsing the `uri` key, the library wraps the underlying exception with the raw connection string — including the plaintext username and password — baked verbatim into the new exception&amp;#39;s message.&lt;/p&gt;
&lt;p&gt;### Details
`ConnectionFactoryConfigurator.load(ConnectionFactory, Map&amp;lt;String,String&amp;gt;, String)` (`src/main/java/com/rabbitmq/client/ConnectionFactoryConfigurator.java`, lines 142-155):&lt;/p&gt;
&lt;p&gt;String uri = properties.get(prefix + &amp;#34;uri&amp;#34;);
    if (uri != null) {
        try {
            cf.setUri(uri);
        } catch (URISyntaxException e) {
            throw new IllegalArgumentException(&amp;#34;Error while setting AMQP URI: &amp;#34; + uri, e);
        } catch (NoSuchAlgorithmException e) {
            throw new IllegalArgumentException(&amp;#34;Error while setting AMQP URI: &amp;#34; + uri, e);
        } catch (KeyManagementException e) {
            throw new IllegalArgumentException(&amp;#34;Error while setting AMQP URI: &amp;#34; + uri, e);
        }
    }&lt;/p&gt;
&lt;p&gt;`uri` is the full AMQP URI — `amqp(s)://username:password@host:port/vhost` — concatenated verbatim into the exception message on any of the three catch branches. No masking/redaction exists anywhere in this class or in `ConnectionFactory.setUri()`. This is the library&amp;#39;s documented Spring-Boot/ops-config entry point (`ConnectionFactory.load(...)`, available since 4.4.0), not obscure internal code.&lt;/p&gt;
&lt;p&gt;RabbitMQ&amp;#39;s own AMQP URI spec (rabbitmq.com/docs/uri-spec) explicitly warns the password &amp;#34;should avo…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: com.rabbitmq:amqp-client&lt;/p&gt;
&lt;p&gt;### Summary
When property-file/Map-based `ConnectionFactory` setup fails while parsing the `uri` key, the library wraps the underlying exception with the raw connection string — including the plaintext username and password — baked verbatim into the new exception&amp;#39;s message.&lt;/p&gt;
&lt;p&gt;### Details
`ConnectionFactoryConfigurator.load(ConnectionFactory, Map&amp;lt;String,String&amp;gt;, String)` (`src/main/java/com/rabbitmq/client/ConnectionFactoryConfigurator.java`, lines 142-155):&lt;/p&gt;
&lt;p&gt;String uri = properties.get(prefix + &amp;#34;uri&amp;#34;);
    if (uri != null) {
        try {
            cf.setUri(uri);
        } catch (URISyntaxException e) {
            throw new IllegalArgumentException(&amp;#34;Error while setting AMQP URI: &amp;#34; + uri, e);
        } catch (NoSuchAlgorithmException e) {
            throw new IllegalArgumentException(&amp;#34;Error while setting AMQP URI: &amp;#34; + uri, e);
        } catch (KeyManagementException e) {
            throw new IllegalArgumentException(&amp;#34;Error while setting AMQP URI: &amp;#34; + uri, e);
        }
    }&lt;/p&gt;
&lt;p&gt;`uri` is the full AMQP URI — `amqp(s)://username:password@host:port/vhost` — concatenated verbatim into the exception message on any of the three catch branches. No masking/redaction exists anywhere in this class or in `ConnectionFactory.setUri()`. This is the library&amp;#39;s documented Spring-Boot/ops-config entry point (`ConnectionFactory.load(...)`, available since 4.4.0), not obscure internal code.&lt;/p&gt;
&lt;p&gt;RabbitMQ&amp;#39;s own AMQP URI spec (rabbitmq.com/docs/uri-spec) explicitly warns the password &amp;#34;should avo…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-h6w7-qmcm-q6xr</guid>
    </item>
  </channel>
</rss>
