ZeroHour
oss-securitypublished ()ingested 1
Part of a story covered by 7 sources: “Apache discloses seven vulnerabilities in Apache Artemis and ActiveMQ Artemis; five rated important, spanning unauthenticated queue creation/deletion, session hijack, credential…” — merged summary and timeline →

CVE-2026-49362: Apache Artemis, Apache ActiveMQ Artemis: Missing Authentication in CORE Protocol Handler Allows Unauthorized Queue Creation

mediumVulnerabilityimportance 38CVE-2026-49362
AI summary · glm-5.3-flash

CVE-2026-49362: unauthenticated attackers can create arbitrary durable queues in ActiveMQ Artemis via the CORE protocol, enabling denial of service.

A missing authentication check in the CORE protocol handler of Apache Artemis and Apache ActiveMQ Artemis, tracked as CVE-2026-49362, lets unauthenticated remote attackers create arbitrary durable queues. This enables unauthorized broker state manipulation and potential denial of service. Affected versions are artemis-server in Apache Artemis 2.50.0 through 2.56.0 and ActiveMQ Artemis 1.0.0 through 2.44.0. Apache rates the issue as important.

  • Missing authentication in CORE protocol handler
  • Unauthenticated remote attackers can create arbitrary durable queues
  • Leads to unauthorized broker state manipulation and potential DoS
  • Rated important by the Apache Security Team

Vulnerabilities mentionedAll →

CVEVulnerabilityCVSSEPSSFlagsAffectedExposurePublished
CVE-2026-49362
Unauthenticated Queue Creation in Apache ActiveMQ Artemis CORE Protocol

CVE-2026-49362 is a missing-authentication flaw (CWE-306) in the CORE protocol handler of Apache ActiveMQ Artemis and Apache Artemis: the broker accepts CORE protocol commands without requiring any credentials. A remote attacker with network access to the broker's CORE acceptor (the default messaging port) can create arbitrary durable queues without authenticating, manipulating broker state without authorization. Because durable queues persist and consume broker resources, an attacker can repeatedly create queues to exhaust storage or memory and cause a denial of service; the queue creation itself also corrupts the intended broker configuration. All Apache ActiveMQ Artemis versions 1.0.0 through 2.44.0 and Apache Artemis versions 2.50.0 through 2.56.0 are affected. There is no CVSS score yet, no public proof-of-concept, and no known exploitation in the wild; the fix is available in version 2.57.0.

Do: Upgrade to Apache Artemis/ActiveMQ Artemis 2.57.0, which fixes the issue. Until patched, restrict network access to the CORE protocol acceptor (the default broker messaging port) to trusted hosts and require authenticated, authorized users on acceptors, disabling anonymous access if present. Check whether brokers are reachable externally on the messaging port and review brokers for unexpected durable queues created without authentication.

7.5<1%
  • Apache ActiveMQ Artemis 1.0.0 through 2.44.0 (inclusive)
  • Apache Artemis 2.50.0 through 2.56.0 (inclusive)
largelikely tens of thousands of broker deployments worldwide, with thousands to tens of thousands internet-exposed on the messaging port
Full article

Posted by Clebert Suconic on Sep 09 Severity: important Affected versions: - Apache Artemis (org.apache.artemis:artemis-server) 2.50.0 through 2.56.0 - Apache ActiveMQ Artemis (org.apache.activemq:artemis-server) 1.0.0 through 2.44.0 Description: An unauthenticated remote attacker can create arbitrary durable queues via the CORE protocol, leading to unauthorized broker state manipulation and potential denial of service. This issue affects Apache Artemis: from 2.50.0 through...

This source does not provide full text. Read it at seclists.org.