Skip to content
VulniPulse
Sign in
Advisory severityCritical9.3Apache Software Foundation

Critical [CVE-2026-27446] Apache Artemis, Apache ActiveMQ Artemis: Auth bypass for Core downstream federation

This critical-severity Apache Software Foundation advisory covers CVE-2026-27446 affecting Apache Artemis, Apache ActiveMQ Artemis, Red Hat JBoss Enterprise Application Platform 7.4 ELS on RHEL 7.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-27446 Source published Source updated

VulniPulse record published Record updated

CVE-2026-27446
Affected products & platforms
Apache Software FoundationMessagingActiveMQ
Open source advisory

Summary

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

This issue affects:

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:

  • 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

Is CVE-2026-27446 exploited?

No exploitation is reported in the sources VulniPulse tracks: CVE-2026-27446 is not in the CISA KEV catalog (checked ) and this advisory does not report exploitation. That is not proof the vulnerability cannot be exploited.

How do I fix CVE-2026-27446?

Upgrade to a fixed release named by Apache:

  • 2.52.0

Confirm against the vendor advisory before you patch.

Affected versions
  • Apache Artemis 2.50.0 through 2.51.0
  • Apache ActiveMQ Artemis 2.11.0 through 2.44.0

Official advisory · high-confidence parse· fetched 4 months ago·verify at source

Fixed versions
  • 2.52.0

Official advisory · high-confidence parse· fetched 4 months ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • 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.
  • This will prevent unauthenticated exploitation of this vulnerability. - Implement and deploy a Core interceptor to deny all Core downstream federation connect packets.

Official advisory · high-confidence parse· fetched 4 months ago·verify at source

Get an email when Apache Messaging (ActiveMQ/Kafka/Pulsar) publishes the next one.

See Apache Messaging (ActiveMQ/Kafka/Pulsar)'s last 90 days of advisories first. Then choose one product with live alerts free for life, or a free month of real-time alerts on everything with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).

Alert me about Apache Messaging (ActiveMQ/Kafka/Pulsar)

More Apache Software Foundation advisories

All Apache Software Foundation advisories

iPhone and Android apps · New on the App Store

Monitor future Apache Software Foundation CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Download on the App StoreGet CVE alerts on AndroidSee app features

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.