CyberSecBulletin
CVE-2026-27446NVD status: Modified

Apache Artemis: Missing Authentication for Critical Functionality

CVE-2026-27446 is a critical-severity missing authentication for critical functionality vulnerability in Apache Artemis from Apache, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected Apache Artemis versions: 2.50.0 through 2.51.0. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 11.4% chance of exploitation within 30 days, which is in the top 3.94% of all scored CVEs.

Patch this week

Critical severity: a successful attack would have severe impact.

What to do

  1. Check which version of Apache Artemis you run against the affected versions below, and install the vendor's latest release.
  2. Read the advisory on lists.apache.org for workarounds and exact fixed builds.
  3. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
ApacheApache Artemis2.50.0 through 2.51.0Not stated
ApacheApache ActiveMQ Artemis2.11.0 through 2.44.0Not stated
Red HatRed Hat AMQ Broker 7.12.6Not specified in the recordNot stated
Red HatRed Hat AMQ Broker 7.13.4Not specified in the recordNot stated
Red HatRed Hat build of Apache Camel 4.18.1 for Spring Boot 3.5.14Not specified in the recordNot stated
Red HatRed Hat JBoss Enterprise Application Platform 7.4 ELS on RHEL 7Not specified in the recordNot stated
Red HatRed Hat JBoss Enterprise Application Platform 7.4 ELS on RHEL 8Not specified in the recordNot stated
Red HatRed Hat JBoss Enterprise Application Platform 7.4 ELS on RHEL 9Not specified in the recordNot stated
Red HatRed Hat JBoss Enterprise Application Platform 8.1.7.GANot specified in the recordNot stated
Red HatRed Hat JBoss Enterprise Application Platform 8.1 for RHEL 8Not specified in the recordNot stated
Red HatRed Hat JBoss Enterprise Application Platform 8.1 for RHEL 9Not specified in the recordNot stated
Red HatRed Hat AMQ ClientsNot specified in the recordNot stated
Red HatRed Hat build of OptaPlanner 8Not specified in the recordNot stated
Red HatRed Hat Fuse 7Not specified in the recordNot stated
Red HatRed Hat JBoss Enterprise Application Platform Expansion PackNot specified in the recordNot stated
Red HatRed Hat OpenShift Dev SpacesNot specified in the recordNot stated
Red HatRed Hat Process Automation 7Not specified in the recordNot stated
Red HatRed Hat Satellite 6Not specified in the recordNot stated
Red HatRed Hat Single Sign-On 7Not specified in the recordNot stated
SiemensOpcenter RDnLall versionsNot stated
ApacheArtemis2.11.0 through 2.44.0; 2.50.0Not stated

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 4.09.3CriticalCNA (apache.org)
CVSS 3.19.8CriticalNVD
CVSS 3.19.1CriticalCNA

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 .

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Missing Authentication for Critical Functionality

The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.

How developers prevent this class of flaw

  • For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using libraries with authentication capabilities such as OpenSSL or the ESAPI Authenticator.
  • When storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to require strong authentication for users who should be allowed to access the data.

More Missing Authentication for Critical Functionality vulnerabilities (CWE-306)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Third-party and government advisories

Other vulnerabilities in Apache Artemis

All Apache Artemis vulnerabilities

Recent Missing Authentication for Critical Functionality vulnerabilities

Spotted an error? Tell us.