# CVE-2026-27446: Apache Artemis, Apache ActiveMQ Artemis: Auth bypass for Core downstream federation > Unauthenticated attackers can force broker federation to exfiltrate or inject messages if Core protocol connections are allowed from untrusted sources. - **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:L/SC:L/SI:L/SA:L`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 4 Mar 2026 - **Updated:** 18 Sep 2026 - **Also known as:** CLSA-2026-1782176242, ECHO-2eda-feb8-1153, GHSA-fw88-pf9m-p947, ROOT-APP-MAVEN-CVE-2026-27446, UBUNTU-CVE-2026-27446 ## What is CVE-2026-27446? CVE-2026-27446 is a critical authentication bypass vulnerability in Apache ActiveMQ Artemis, published on 4 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description 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 "artemis" acceptor listening on port 61616. See the "protocols" 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 vulnerability. - Implement and deploy a Core interceptor to deny all Core downstream federation connect packets. Such packets have a type of (int) -16 or (byte) 0xfffffff0. Documentation for interceptors is available at  https://artemis.apache.org/components/artemis/documentation/latest/intercepting-operations.html . Weakness: CWE-306 (Missing Authentication for Critical Functionality) ## Which versions are affected by CVE-2026-27446? 4 open source packages ship an affected version, including org.apache.activemq:artemis-server and org.apache.artemis:artemis-server. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.apache.activemq:artemis-server` | Maven | From 2.11.0 to 2.44.0 | None | | `org.apache.activemq:artemis-server` | Maven | From 2.11.0 to 2.44.0 | None | | `org.apache.artemis:artemis-server` | Maven | From 2.50.0 | 2.52.0 | | `org.apache.artemis:artemis-server` | Maven | From 2.50.0 | 2.52.0 | Products: Apache Artemis. ## How do I fix CVE-2026-27446? Upgrade to a fixed version. ## Is CVE-2026-27446 being exploited? There is no known exploitation of CVE-2026-27446 in the wild and no public exploit code. ## Other vulnerabilities in Apache ActiveMQ Artemis - [CVE-2026-57967](https://insights.sbomify.com/CVE-2026-57967/): Apache Artemis, Apache ActiveMQ Artemis: Missing authentication on CORE protocol session reattachment (critical 9.8) - [CVE-2026-49364](https://insights.sbomify.com/CVE-2026-49364/): Information disclosure in Apache ActiveMQ Artemis (critical 9.1) - [CVE-2026-67593](https://insights.sbomify.com/CVE-2026-67593/): Missing authorization in Apache ActiveMQ Artemis (critical 9.1) - [CVE-2023-50780](https://insights.sbomify.com/CVE-2023-50780/): Apache ActiveMQ Artemis: Authenticated users could perform RCE via Jolokia MBeans (high 8.8) - [CVE-2026-49362](https://insights.sbomify.com/CVE-2026-49362/): Missing authorization in Apache ActiveMQ Artemis (high 7.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-27446 and fix it if it is affected. What it is: CVE-2026-27446 is a critical authentication bypass vulnerability in Apache ActiveMQ Artemis, published on 4 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-27446 in the wild and no public exploit code. Affected packages and fixed versions: - org.apache.activemq:artemis-server (Maven): affected from 2.11.0 up to 2.44.0; no fix listed - org.apache.activemq:artemis-server (Maven): affected from 2.11.0 up to 2.44.0; no fix listed - org.apache.artemis:artemis-server (Maven): affected from 2.50.0; fixed in 2.52.0 - org.apache.artemis:artemis-server (Maven): affected from 2.50.0; fixed in 2.52.0 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-27446/ (Markdown: https://insights.sbomify.com/CVE-2026-27446/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-27446 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-27446 - OSV: https://osv.dev/vulnerability/CVE-2026-27446 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-27446/ Summaries are generated and may contain mistakes; the official description above is the record.