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-75880: Apache Artemis, Apache ActiveMQ Artemis: Message selector wildcard handling could lead to denial of service

mediumVulnerabilityimportance 30CVE-2026-75880
AI summary · glm-5.3-flash

CVE-2026-75880: authenticated ActiveMQ Artemis clients can cause denial of service via crafted selector wildcard handling in affected versions.

An authenticated client can attach a consumer with a selector containing crafted wildcard usage, causing excessive evaluation during message delivery attempts that occupies a shared broker thread and leads to denial of service. Affected versions are Apache Artemis artemis-selector 2.50.0 through 2.56.0 and Apache ActiveMQ Artemis artemis-selector 1.0.0 through 2.44.0. Apache rates the issue moderate.

  • Authenticated clients can trigger broker denial of service via crafted selector wildcards.
  • Affects artemis-selector 2.50.0-2.56.0 (Artemis) and 1.0.0-2.44.0 (ActiveMQ Artemis).
  • Rated moderate by Apache.

Vulnerabilities mentionedAll →

CVEVulnerabilityCVSSEPSSFlagsAffectedExposurePublished
CVE-2026-75880
Authenticated DoS via crafted wildcard message selectors in Apache ActiveMQ Artemis

Apache ActiveMQ Artemis fails to bound the evaluation cost of message selectors, so a selector with crafted wildcard usage can trigger excessive processing (CWE-1333) each time the broker attempts message delivery. An authenticated client triggers it by attaching a consumer whose selector contains the crafted wildcards, and each delivery attempt then occupies a shared broker thread for a disproportionate amount of time. By sustaining this load (with one or more such consumers), the attacker can tie up broker threads and stall or degrade message delivery for other clients, achieving denial of service with no privilege escalation or data exposure. All users running Apache Artemis 2.50.0 through 2.56.0 or Apache ActiveMQ Artemis 1.0.0 through 2.44.0 are affected, which in practice covers essentially every Artemis release before 2.57.0 across standalone and embedded broker deployments. The flaw has no CVSS score yet, no known public proof-of-concept, is not listed in CISA KEV, and there are no known reports of exploitation in the wild.

Do: Upgrade to Apache Artemis 2.57.0, the fix version cited in the advisory. As an interim measure, restrict broker access to trusted authenticated clients and review consumer configurations that use wildcard-heavy selectors, since valid credentials are required to trigger the flaw. Until a CVSS score is published, prioritize patching internet-reachable or multi-tenant brokers where authenticated clients could saturate delivery threads.

6.5<1%
  • Apache Artemis 2.50.0 through 2.56.0
  • Apache ActiveMQ Artemis 1.0.0 through 2.44.0
largetens of thousands of broker deployments (of which only a few thousand are internet-exposed)
Full article

Posted by Clebert Suconic on Sep 09 Severity: moderate Affected versions: - Apache Artemis (org.apache.artemis:artemis-selector) 2.50.0 through 2.56.0 - Apache ActiveMQ Artemis (org.apache.activemq:artemis-selector) 1.0.0 through 2.44.0 Description: An authenticated client could attach a consumer with a selector containing crafted wildcard usage that results in excessive evaluation during message delivery attempts, occupying a shared broker thread and leading to denial of...

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