Red Hat Security Advisory: Red Hat AMQ Broker 7.13.4 release and security update
AMQ Broker is a high-performance messaging implementation based on ActiveMQ Artemis. It uses an asynchronous journal for fast message persistence, and supports multiple languages, protocols, and platforms. This release of Red Hat AMQ Broker 7.13.4 includes security and bug fixes, and enhancements. For further information, refer to the release notes linked to in the References section. Security Fix(es): * (CVE-2026-27446) artemis-server: Apache Artemis, Apache ActiveMQ Artemis: Message injection and exfiltration due to missing authentication For more details about the security issue(s), including the impact, a CVSS score, and other related information, refer to the CVE page(s) listed in the References section.
AI Analysis
Technical Summary
CVE-2026-27446 is a CWE-306 Missing Authentication for Critical Function vulnerability in Apache Artemis and Apache ActiveMQ Artemis. It allows an unauthenticated remote attacker to use the Core protocol to coerce a broker into establishing an outbound Core federation connection to an attacker-controlled rogue broker. This can result in unauthorized message injection and exfiltration from any queue. The vulnerability affects Apache Artemis versions 2.50.0 through 2.51.0 and Apache ActiveMQ Artemis versions 2.11.0 through 2.44.0. The vulnerability requires that the broker accepts incoming Core protocol connections from untrusted sources and has outbound connectivity to attacker-controlled systems. The vulnerability does not enable remote code execution or system compromise but impacts confidentiality and integrity of messages. Red Hat rates this flaw as Important severity, while the CVSS v4.0 base score is 9.3 (critical). Mitigations include restricting Core protocol support on acceptors receiving connections from untrusted sources or enabling two-way SSL with certificate-based authentication. A fix is available in Apache Artemis version 2.52.0.
Potential Impact
An unauthenticated attacker can exploit this vulnerability to inject messages into any queue or exfiltrate messages from any queue by forcing the broker to connect to a rogue broker controlled by the attacker. This compromises the confidentiality and integrity of messages handled by the broker. The vulnerability does not allow remote code execution or cause service disruption. Exploitation requires the broker to accept inbound Core protocol connections from untrusted sources and have outbound connectivity to attacker-controlled systems.
Mitigation Recommendations
A fix is available in Apache Artemis version 2.52.0; users are strongly recommended to upgrade to this version. Alternatively, mitigate the issue by removing Core protocol support from acceptors that receive connections from untrusted sources by modifying the acceptor URL to exclude the Core protocol using the "protocols" parameter. Another mitigation is to configure two-way SSL with certificate-based authentication to prevent unauthenticated exploitation. A service restart or reload may be required for changes to take effect.
Red Hat Security Advisory: Red Hat AMQ Broker 7.13.4 release and security update
Description
AMQ Broker is a high-performance messaging implementation based on ActiveMQ Artemis. It uses an asynchronous journal for fast message persistence, and supports multiple languages, protocols, and platforms. This release of Red Hat AMQ Broker 7.13.4 includes security and bug fixes, and enhancements. For further information, refer to the release notes linked to in the References section. Security Fix(es): * (CVE-2026-27446) artemis-server: Apache Artemis, Apache ActiveMQ Artemis: Message injection and exfiltration due to missing authentication For more details about the security issue(s), including the impact, a CVSS score, and other related information, refer to the CVE page(s) listed in the References section.
Affected software
pkg:rpm/redhat/jboss-amq-brokerRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-27446 is a CWE-306 Missing Authentication for Critical Function vulnerability in Apache Artemis and Apache ActiveMQ Artemis. It allows an unauthenticated remote attacker to use the Core protocol to coerce a broker into establishing an outbound Core federation connection to an attacker-controlled rogue broker. This can result in unauthorized message injection and exfiltration from any queue. The vulnerability affects Apache Artemis versions 2.50.0 through 2.51.0 and Apache ActiveMQ Artemis versions 2.11.0 through 2.44.0. The vulnerability requires that the broker accepts incoming Core protocol connections from untrusted sources and has outbound connectivity to attacker-controlled systems. The vulnerability does not enable remote code execution or system compromise but impacts confidentiality and integrity of messages. Red Hat rates this flaw as Important severity, while the CVSS v4.0 base score is 9.3 (critical). Mitigations include restricting Core protocol support on acceptors receiving connections from untrusted sources or enabling two-way SSL with certificate-based authentication. A fix is available in Apache Artemis version 2.52.0.
Potential Impact
An unauthenticated attacker can exploit this vulnerability to inject messages into any queue or exfiltrate messages from any queue by forcing the broker to connect to a rogue broker controlled by the attacker. This compromises the confidentiality and integrity of messages handled by the broker. The vulnerability does not allow remote code execution or cause service disruption. Exploitation requires the broker to accept inbound Core protocol connections from untrusted sources and have outbound connectivity to attacker-controlled systems.
Mitigation Recommendations
A fix is available in Apache Artemis version 2.52.0; users are strongly recommended to upgrade to this version. Alternatively, mitigate the issue by removing Core protocol support from acceptors that receive connections from untrusted sources by modifying the acceptor URL to exclude the Core protocol using the "protocols" parameter. Another mitigation is to configure two-way SSL with certificate-based authentication to prevent unauthenticated exploitation. A service restart or reload may be required for changes to take effect.
Technical Details
- Gcve Source
- db.gcve.eu
- Csaf Category
- csaf_security_advisory
- Csaf Version
- 2.0
- Publisher
- Red Hat Product Security
- Advisory Id
- RHSA-2026:3955
- Cve Count
- 1
- State
- PUBLISHED
Threat ID: 6a175ee3e29bf47b50edacd8
Added to database: 05/27/2026, 21:15:15 UTC
Last enriched: 08/12/2026, 18:14:26 UTC
Last updated: 09/15/2026, 06:40:42 UTC
Views: 115
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.