https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 08:03:54 +0000 https://cve.radiocsirt.org/vuln/cve-2026-27446 <p><strong>Affected:</strong> Apache Software Foundation Apache Artemis, Apache Software Foundation Apache ActiveMQ Artemis, Siemens Opcenter RDnL, Red Hat AMQ Broker 7.12.6, Red Hat AMQ Broker 7.13.4, Red Hat build of Apache Camel 4.18.1 for Spring Boot 3.5.14, Red Hat JBoss Enterprise Application Platform 7.4 ELS on RHEL 7, Red Hat JBoss Enterprise Application Platform 7.4 ELS on RHEL 8, Red Hat JBoss Enterprise Application Platform 7.4 ELS on RHEL 9, Red Hat JBoss Enterprise Application Platform 8.1.7.GA and 10 more</p> <p>Missing Authentication for Critical Function (CWE-306) vulnerability in Apache Artemis, Apache ActiveMQ Artemis. An unauthenticated remote attacker can use the Core protocol to force a target broker to establish an outbound Core federation connection to an attacker-controlled rogue broker. This could potentially result in message injection into any queue and/or message exfiltration from any queue via the rogue broker. This impacts environments that allow both:</p> <p>- incoming Core protocol connections from untrusted sources to the broker</p> <p>- outgoing Core protocol connections from the broker to untrusted targets</p> <p>This issue affects:</p> <p>- Apache Artemis from 2.50.0 through 2.51.0</p> <p>- Apache ActiveMQ Artemis from 2.11.0 through 2.44.0.</p> <p>Users are recommended to upgrade to Apache Artemis version 2.52.0, which fixes the issue.</p> <p>The issue can be mitigated by one of the following:</p> <p>- Remove Core protocol support from any acceptor receiving connections from untrusted sources. Incoming Core protocol connections are supported by default via the &#34;artemis&#34; acceptor listening on port 61616. See the &#34;protocols&#34; URL parameter configured for the acceptor. An acceptor URL without this parameter supports all protocols by default, including Core.</p> <p>- Use two-way SSL (i.e. certificate-based authentication) in order to force every client to present the proper SSL certificate when establishing a connection before any message protocol handshake is attempted. This will prevent unauthenticated exploitation…</p> <p><strong>Affected:</strong> Apache Software Foundation Apache Artemis, Apache Software Foundation Apache ActiveMQ Artemis, Siemens Opcenter RDnL, Red Hat AMQ Broker 7.12.6, Red Hat AMQ Broker 7.13.4, Red Hat build of Apache Camel 4.18.1 for Spring Boot 3.5.14, Red Hat JBoss Enterprise Application Platform 7.4 ELS on RHEL 7, Red Hat JBoss Enterprise Application Platform 7.4 ELS on RHEL 8, Red Hat JBoss Enterprise Application Platform 7.4 ELS on RHEL 9, Red Hat JBoss Enterprise Application Platform 8.1.7.GA and 10 more</p> <p>Missing Authentication for Critical Function (CWE-306) vulnerability in Apache Artemis, Apache ActiveMQ Artemis. An unauthenticated remote attacker can use the Core protocol to force a target broker to establish an outbound Core federation connection to an attacker-controlled rogue broker. This could potentially result in message injection into any queue and/or message exfiltration from any queue via the rogue broker. This impacts environments that allow both:</p> <p>- incoming Core protocol connections from untrusted sources to the broker</p> <p>- outgoing Core protocol connections from the broker to untrusted targets</p> <p>This issue affects:</p> <p>- Apache Artemis from 2.50.0 through 2.51.0</p> <p>- Apache ActiveMQ Artemis from 2.11.0 through 2.44.0.</p> <p>Users are recommended to upgrade to Apache Artemis version 2.52.0, which fixes the issue.</p> <p>The issue can be mitigated by one of the following:</p> <p>- Remove Core protocol support from any acceptor receiving connections from untrusted sources. Incoming Core protocol connections are supported by default via the &#34;artemis&#34; acceptor listening on port 61616. See the &#34;protocols&#34; URL parameter configured for the acceptor. An acceptor URL without this parameter supports all protocols by default, including Core.</p> <p>- Use two-way SSL (i.e. certificate-based authentication) in order to force every client to present the proper SSL certificate when establishing a connection before any message protocol handshake is attempted. This will prevent unauthenticated exploitation…</p> https://cve.radiocsirt.org/vuln/cve-2026-27446