https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 11:24:27 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-371765 EUVD-2026-371765 https://cve.radiocsirt.org/vuln/euvd-2026-371765 https://cve.radiocsirt.org/vuln/fkie_cve-2026-27446 <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>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/fkie_cve-2026-27446 https://cve.radiocsirt.org/vuln/ghsa-fw88-pf9m-p947 <p><strong>Affected:</strong> Maven: org.apache.activemq:artemis-server, Maven: org.apache.artemis:artemis-server</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 either 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 exploitati…</p> <p><strong>Affected:</strong> Maven: org.apache.activemq:artemis-server, Maven: org.apache.artemis:artemis-server</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 either 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 exploitati…</p> https://cve.radiocsirt.org/vuln/ghsa-fw88-pf9m-p947 https://cve.radiocsirt.org/vuln/icsa-26-134-09 <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: - incoming Core protocol connections from untrusted sources to the broker - outgoing Core protocol connections from the broker to untrusted targets ActiveMQ Artemis is used for Async processing between different web applications. Any message processed by a consumer will apply schema validation first. Message sent by Opcenter RD&amp;L to ActiveMQ does not contain any confidential information. Breaking the integrity of a message has a low impact (missing auto refresh functionality). Access to ActiveMQ is only allowed within the Data Center. Inbound connections to the Data Center to port 61616 (default) should be blocked.</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: - incoming Core protocol connections from untrusted sources to the broker - outgoing Core protocol connections from the broker to untrusted targets ActiveMQ Artemis is used for Async processing between different web applications. Any message processed by a consumer will apply schema validation first. Message sent by Opcenter RD&amp;L to ActiveMQ does not contain any confidential information. Breaking the integrity of a message has a low impact (missing auto refresh functionality). Access to ActiveMQ is only allowed within the Data Center. Inbound connections to the Data Center to port 61616 (default) should be blocked.</p> https://cve.radiocsirt.org/vuln/icsa-26-134-09 https://cve.radiocsirt.org/vuln/ncsc-2026-0147 NCSC-2026-0147 https://cve.radiocsirt.org/vuln/ncsc-2026-0147 https://cve.radiocsirt.org/vuln/rhsa-2026:17668 <p>bouncycastle: BC-JAVA: GOSTCTR implementation unable to process more than 255 blocks correctly org.codehaus.plexus:plexus-utils: Plexus-utils: Directory Traversal in extractFile method bouncycastle: BC-JAVA: LDAP injection vulnerability in LDAPStoreHelper.java org.eclipse.jetty/jetty-http: HTTP request smuggling via chunked extension quoted-string parsing bouncycastle: BC-JAVA: unbounded PGP AEAD chunk size leads to pre-auth resource exhaustion bouncycastle: BC-JAVA: PKIX draft CompositeVerifier accepts empty signature sequence as valid org.eclipse.jetty.ee10/jetty-ee10: early return from the JASPIAuthenticator class without clearing ThreadLocal variables camel-infinispan: camel-infinispan: Remote Code Execution via Unsafe Deserialization Spring Boot: Spring Boot: Authentication bypass via misconfigured Health Group additional path org.apache.artemis:artemis-server: org.apache.activemq:artemis-server: Apache Artemis, Apache ActiveMQ Artemis: Message injection and exfiltration due to missing authentication Apache Camel: camel-coap: Apache Camel camel-coap: Remote code execution via CoAP URI query parameter injection Apache Camel: Camel-Mail: Camel-Mail: Altered application behavior via header injection io.netty/netty-codec-http: Netty: Request smuggling via incorrect parsing of HTTP/1.1 chunked transfer encoding extension values netty: Netty: Denial of Service via HTTP/2 CONTINUATION frame flood Apache Kafka Clients: Apache Kafka Clients: Information disclosure and data corru…</p> <p>bouncycastle: BC-JAVA: GOSTCTR implementation unable to process more than 255 blocks correctly org.codehaus.plexus:plexus-utils: Plexus-utils: Directory Traversal in extractFile method bouncycastle: BC-JAVA: LDAP injection vulnerability in LDAPStoreHelper.java org.eclipse.jetty/jetty-http: HTTP request smuggling via chunked extension quoted-string parsing bouncycastle: BC-JAVA: unbounded PGP AEAD chunk size leads to pre-auth resource exhaustion bouncycastle: BC-JAVA: PKIX draft CompositeVerifier accepts empty signature sequence as valid org.eclipse.jetty.ee10/jetty-ee10: early return from the JASPIAuthenticator class without clearing ThreadLocal variables camel-infinispan: camel-infinispan: Remote Code Execution via Unsafe Deserialization Spring Boot: Spring Boot: Authentication bypass via misconfigured Health Group additional path org.apache.artemis:artemis-server: org.apache.activemq:artemis-server: Apache Artemis, Apache ActiveMQ Artemis: Message injection and exfiltration due to missing authentication Apache Camel: camel-coap: Apache Camel camel-coap: Remote code execution via CoAP URI query parameter injection Apache Camel: Camel-Mail: Camel-Mail: Altered application behavior via header injection io.netty/netty-codec-http: Netty: Request smuggling via incorrect parsing of HTTP/1.1 chunked transfer encoding extension values netty: Netty: Denial of Service via HTTP/2 CONTINUATION frame flood Apache Kafka Clients: Apache Kafka Clients: Information disclosure and data corru…</p> https://cve.radiocsirt.org/vuln/rhsa-2026:17668 https://cve.radiocsirt.org/vuln/ssa-085541 <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: - incoming Core protocol connections from untrusted sources to the broker - outgoing Core protocol connections from the broker to untrusted targets ActiveMQ Artemis is used for Async processing between different web applications. Any message processed by a consumer will apply schema validation first. Message sent by Opcenter RD&amp;L to ActiveMQ does not contain any confidential information. Breaking the integrity of a message has a low impact (missing auto refresh functionality). Access to ActiveMQ is only allowed within the Data Center. Inbound connections to the Data Center to port 61616 (default) should be blocked.</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: - incoming Core protocol connections from untrusted sources to the broker - outgoing Core protocol connections from the broker to untrusted targets ActiveMQ Artemis is used for Async processing between different web applications. Any message processed by a consumer will apply schema validation first. Message sent by Opcenter RD&amp;L to ActiveMQ does not contain any confidential information. Breaking the integrity of a message has a low impact (missing auto refresh functionality). Access to ActiveMQ is only allowed within the Data Center. Inbound connections to the Data Center to port 61616 (default) should be blocked.</p> https://cve.radiocsirt.org/vuln/ssa-085541 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-27446 <p><strong>Affected:</strong> Ubuntu:Pro:16.04:LTS: activemq, Ubuntu:Pro:18.04:LTS: activemq, Ubuntu:Pro:20.04:LTS: activemq, Ubuntu:Pro:22.04:LTS: activemq, Ubuntu:24.04:LTS: activemq, Ubuntu:25.10: activemq, Ubuntu:26.04:LTS: activemq</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: - incoming Core protocol connections from untrusted sources to the broker - outgoing Core protocol connections from the broker to untrusted targets This issue affects: - Apache Artemis from 2.50.0 through 2.51.0 - Apache ActiveMQ Artemis from 2.11.0 through 2.44.0. Users are recommended to upgrade to Apache Artemis version 2.52.0, which fixes the issue. The issue can be mitigated by one of the following: - 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. - 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 of this v…</p> <p><strong>Affected:</strong> Ubuntu:Pro:16.04:LTS: activemq, Ubuntu:Pro:18.04:LTS: activemq, Ubuntu:Pro:20.04:LTS: activemq, Ubuntu:Pro:22.04:LTS: activemq, Ubuntu:24.04:LTS: activemq, Ubuntu:25.10: activemq, Ubuntu:26.04:LTS: activemq</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: - incoming Core protocol connections from untrusted sources to the broker - outgoing Core protocol connections from the broker to untrusted targets This issue affects: - Apache Artemis from 2.50.0 through 2.51.0 - Apache ActiveMQ Artemis from 2.11.0 through 2.44.0. Users are recommended to upgrade to Apache Artemis version 2.52.0, which fixes the issue. The issue can be mitigated by one of the following: - 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. - 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 of this v…</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-27446 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0591 <p>Ein Angreifer kann mehrere Schwachstellen in Apache ActiveMQ/Artemis ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, und um Sicherheitsvorkehrungen zu umgehen.</p> <p>Ein Angreifer kann mehrere Schwachstellen in Apache ActiveMQ/Artemis ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, und um Sicherheitsvorkehrungen zu umgehen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0591