Vulnary
← back to the feed
Critical· 9.3official fix available

CVE-2026-27446

Apache Artemis and ActiveMQ Artemis versions 2.50.0‑2.51.0 and 2.11.0‑2.44.0 have a missing authentication flaw that lets an unauthenticated attacker force the broker to open an outbound connection to a rogue broker. This can let the attacker inject messages into queues or steal messages from them.

publishedMar 4, 2026
last modifiedAug 4, 2026
sourcesNVD
severity · cvss
9.3
critical · how bad it is
exploitation · epss
10%
95th percentile · chance of exploitation in 30 days
(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →
auto-deletes from the system
counting…on Sep 3, 2026

An official fix is available, so this entry is kept for 30 days and then removed automatically.

01

Who is affected

Apache Artemis 2.50.0 through 2.51.0 and Apache ActiveMQ Artemis 2.11.0 through 2.44.0, used by organizations running these message brokers.

02

Real-world impact

An attacker can inject malicious messages into any queue or exfiltrate sensitive messages by hijacking the broker’s federation connection to a rogue broker.

03

Why this severity

The CVSS score of 9.3 reflects that the vulnerability is exploitable remotely without authentication, has a low attack complexity, and can compromise confidentiality and integrity of all messages handled by the broker.

04

What to do about it

official fix available
recommended steps
  1. 01Upgrade Apache Artemis to version 2.52.0 or later.
  2. 02Restart the broker to apply the update.
interim mitigations
  • ›Remove Core protocol support from any acceptor that receives connections from untrusted sources.
  • ›Use two‑way SSL (certificate‑based authentication) for all client connections.
  • ›Deploy a Core interceptor to deny all Core downstream federation connect packets.

NVD vendor advisory

05

Timeline

  1. Mar 4, 2026 · Mar 4, 2026
    Published
    Disclosed and added to the National Vulnerability Database.
  2. Aug 4, 2026 · 22h ago
    Advisory updated
    The NVD record was last revised.
  3. Aug 4, 2026 · 20h ago
    Official fix available
    A vendor patch or mitigation now exists — see the remediation steps above.
06

How it’s attacked

Attack vectorNetwork (remote)
Attack complexityLow
Attack requirementsNone
Privileges requiredNone
User interactionNone needed
Confidentiality impactHigh
Integrity impactHigh
Availability impactLow
07

References & advisories

NVD advisory ↗Search advisories ↗
(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →