<?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://cve.radiocsirt.org</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, 19 Oct 2026 05:44:31 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-08197</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-08197</link>
      <description>bdu:2025-08197</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-08197</guid>
    </item>
    <item>
      <title>EUVD-2026-226759</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-226759</link>
      <description>EUVD-2026-226759</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-226759</guid>
    </item>
    <item>
      <title>fkie_cve-2025-27427</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-27427</link>
      <description>&lt;p&gt;A vulnerability exists in Apache ActiveMQ Artemis whereby a user with the createDurableQueue or createNonDurableQueue permission on an address can augment the routing-type supported by that address even if said user doesn&amp;#39;t have the createAddress permission for that particular address. When combined with the send permission and automatic queue creation a user could successfully send a message with a routing-type not supported by the address when that message should actually be rejected on the basis that the user doesn&amp;#39;t have permission to change the routing-type of the address.&lt;/p&gt;
&lt;p&gt;This issue affects Apache ActiveMQ Artemis from 2.0.0 through 2.39.0.&lt;/p&gt;
&lt;p&gt;Users are recommended to upgrade to version 2.40.0 which fixes the issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;A vulnerability exists in Apache ActiveMQ Artemis whereby a user with the createDurableQueue or createNonDurableQueue permission on an address can augment the routing-type supported by that address even if said user doesn&amp;#39;t have the createAddress permission for that particular address. When combined with the send permission and automatic queue creation a user could successfully send a message with a routing-type not supported by the address when that message should actually be rejected on the basis that the user doesn&amp;#39;t have permission to change the routing-type of the address.&lt;/p&gt;
&lt;p&gt;This issue affects Apache ActiveMQ Artemis from 2.0.0 through 2.39.0.&lt;/p&gt;
&lt;p&gt;Users are recommended to upgrade to version 2.40.0 which fixes the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-27427</guid>
    </item>
    <item>
      <title>GHSA-3w85-5p9g-h334 — Apache ActiveMQ Artemis User Without Create Address Permissions can Modify Address Routing-Type</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-3w85-5p9g-h334</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.apache.activemq:artemis-server&lt;/p&gt;
&lt;p&gt;A vulnerability exists in Apache ActiveMQ Artemis whereby a user with the createDurableQueue or createNonDurableQueue permission on an address can augment the routing-type supported by that address even if said user doesn&amp;#39;t have the createAddress permission for that particular address. When combined with the send permission and automatic queue creation a user could successfully send a message with a routing-type not supported by the address when that message should actually be rejected on the basis that the user doesn&amp;#39;t have permission to change the routing-type of the address.&lt;/p&gt;
&lt;p&gt;This issue affects Apache ActiveMQ Artemis from 2.0.0 through 2.39.0.&lt;/p&gt;
&lt;p&gt;Users are recommended to upgrade to version 2.40.0 which fixes the issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.apache.activemq:artemis-server&lt;/p&gt;
&lt;p&gt;A vulnerability exists in Apache ActiveMQ Artemis whereby a user with the createDurableQueue or createNonDurableQueue permission on an address can augment the routing-type supported by that address even if said user doesn&amp;#39;t have the createAddress permission for that particular address. When combined with the send permission and automatic queue creation a user could successfully send a message with a routing-type not supported by the address when that message should actually be rejected on the basis that the user doesn&amp;#39;t have permission to change the routing-type of the address.&lt;/p&gt;
&lt;p&gt;This issue affects Apache ActiveMQ Artemis from 2.0.0 through 2.39.0.&lt;/p&gt;
&lt;p&gt;Users are recommended to upgrade to version 2.40.0 which fixes the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-3w85-5p9g-h334</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-0670 — Apache ActiveMQ: Schwachstelle ermöglicht Umgehen von Sicherheitsvorkehrungen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0670</link>
      <description>&lt;p&gt;Ein entfernter, authentisierter Angreifer kann eine Schwachstelle in Apache ActiveMQ ausnutzen, um Sicherheitsvorkehrungen zu umgehen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, authentisierter Angreifer kann eine Schwachstelle in Apache ActiveMQ ausnutzen, um Sicherheitsvorkehrungen zu umgehen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0670</guid>
    </item>
  </channel>
</rss>
