BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-49363High confidence

Apache Artemis, Apache ActiveMQ Artemis: Pre-Authentication Information Disclosure in CORE Protocol Topology Subscription

Apache Software Foundation · Apache Artemis

7.5HighCVSS 3.1
Recommended action
Within 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.80% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Apache Software Foundation Apache Artemis and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 30 daysRemediation target: Within 180 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-49363 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityartemis-server: artemis-server: Pre-auth topology disclosure via CORE SUBSCRIBE_TOPOLOGY_V2 on channel0
2 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • artemis-server as a component of Red Hat JBoss Enterprise Application Platform 7
  • artemis-server as a component of Red Hat JBoss Enterprise Application Platform Expansion Pack
Summary
A missing authentication vulnerability was found in Apache ActiveMQ Artemis. The SUBSCRIBE_TOPOLOGY_V2 handler in CoreProtocolManager.LocalChannelHandler.handlePacket() processes topology subscription requests on channel0 with zero authentication -- no call to getSecurityStore(), no credential verification, no subject validation. An unauthenticated attacker can send a single 5-byte packet on the CORE protocol (via :8080 HTTP-upgrade in EAP or :61616 in AMQ Broker) to obtain the broker's nodeID (type-1 UUID embedding MAC address), internal hostname/IP, port numbers, connector configurations, and backup/scale-down group names. In clustered deployments, a persistent ClusterTopologyListener is registered that continuously pushes all topology changes to the unauthenticated client. This contrasts with the federation handler in the same file which was fixed via ARTEMIS-5928 (CVE-2026-27446). The leaked nodeID UUID seed directly enables session-name brute-force for REATTACH_SESSION session hijack.
Remediation
Before applying the update, make sure all previously released errata relevant to your system have been applied. Also, back up your existing installation, including all applications, configuration files, databases and database settings. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-75249

No EUVD known-exploited evidence

An unauthenticated remote attacker connecting with the CORE protocol can discover cluster node details by sending a SUBSCRIBE_TOPOLOGY request prior to authentication. This issue affects Apache Artemis: from 2.50.0 through 2.56.0; Apache ActiveMQ Artemis: from 1.0.0 through 2.44.0. Users are recommended to upgrade to version 2.57.0, which fixes the issue.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
7.5 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
01

What, why and how

An unauthenticated remote attacker connecting with the CORE protocol can discover cluster node details by sending a SUBSCRIBE_TOPOLOGY request prior to authentication. This issue affects Apache Artemis: from 2.50.0 through 2.56.0; Apache ActiveMQ Artemis: from 1.0.0 through 2.44.0. Users are recommended to upgrade to version 2.57.0, which fixes the issue.

What

An unauthenticated remote attacker connecting with the CORE protocol can discover cluster node details by sending a SUBSCRIBE_TOPOLOGY request prior to authentication. This issue affects Apache Artemis: from 2.50.0 through 2.56.0; Apache ActiveMQ Artemis: from 1.0.0 through 2.44.0. Users are recommended to upgrade to version 2.57.0, which fixes the issue.

Why

A security-sensitive function is reachable without the authentication check that should protect it.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

An unauthenticated remote attacker connecting with the CORE protocol can discover cluster node details by sending a SUBSCRIBE_TOPOLOGY request prior to authentication. This issue affects Apache Artemis: from 2.50.0 through 2.56.0; Apache ActiveMQ Artemis: from 1.0.0 through 2.44.0. Users are recommended to upgrade to version 2.57.0, which fixes the issue.

Why

A security-sensitive function is reachable without the authentication check that should protect it.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Missing Authentication for Critical Function → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-306 ↗

CWE-306: Missing Authentication for Critical Function. The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.INoneIntegrity impact: No direct loss is represented by this metric.ANoneAvailability impact: No direct loss is represented by this metric.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-306
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2026-75249Official EUVD mapping

An unauthenticated remote attacker connecting with the CORE protocol can discover cluster node details by sending a SUBSCRIBE_TOPOLOGY request prior to authentication. This issue affects Apache Artemis: from 2.50.0 through 2.56.0; Apache ActiveMQ Artemis: from 1.0.0 through 2.44.0. Users are recommended to upgrade to version 2.57.0, which fixes the issue.

Official EUVD record ↗
BSI · German · WID-SEC-2026-3289Apache ActiveMQ Artemis: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Apache ActiveMQ Artemis ausnutzen, um Sicherheitsvorkehrungen zu umgehen, authentifizierte Sitzungen zu kapern, Daten zu manipulieren oder offenzulegen oder Denial-of-Service-Zustände herbeizuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260916Security Bulletin 16 Sep 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 16 Sep 2026, published on 16 September 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-033653Apache Software FoundationのApache Artemisにおける重要な機能に対する認証の欠如に関する脆弱性

認証前にSUBSCRIBE_TOPOLOGYリクエストを送信することで、COREプロトコルで接続する認証されていないリモート攻撃者がクラスタノードの詳細を発見できるという問題があります。この問題はApache Artemisのバージョン2.50.0から2.56.0まで、およびApache ActiveMQ Artemisのバージョン1.0.0から2.44.0までに影響します。ユーザーには、この問題を修正したバージョン2.57.0へアップグレードすることを推奨します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
Fixed
Action
Before applying the update, make sure all previously released errata relevant to your system have been applied. Also, back up your existing installation, including all applications, configuration files, databases and database settings. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 10 Sept 2026 · Last source change 10 Sept 2026, 15:55 UTC · CWE-306 · Missing Authentication for Critical Function

CVE recordCVE.org · 5.2
CVSS sourceCISA ADP
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-09-10
European sourceENISA EUVD · EUVD-2026-75249
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    Apache Artemis: 2.50.0 ≤ 2.56.0; Apache ActiveMQ Artemis: 1.0.0 ≤ 2.44.0 · Fixed: Before applying the update, back up your existing installation, including all applications, configuration files, databases and database settings. The References section of this erratum contains a download link (you must log in to download the update).
    After
    Apache Artemis: 2.50.0 ≤ 2.56.0; Apache ActiveMQ Artemis: 1.0.0 ≤ 2.44.0 · Fixed: Before applying the update, make sure all previously released errata relevant to your system have been applied. Also, back up your existing installation, including all applications, configuration files, databases and database settings. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
    Red Hat Product Security ↗
  2. Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2026-49363 to remediation: access.redhat.com/CVE-2026-49363.
    Before
    remediation: access.redhat.com/CVE-2026-49363
    After
    remediation: access.redhat.com/CVE-2026-49363
    Red Hat Product Security ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    artemis-server as a component of Red Hat JBoss Enterprise Application Platform 7; artemis-server as a component of Red Hat JBoss Enterprise Application Platform 8; artemis-server as a component of Red Hat JBoss Enterprise Application Platform Expansion Pack · Fixed: Red Hat AMQ Broker 7.13.6; Red Hat AMQ Broker 7.14.1
    After
    artemis-server as a component of Red Hat JBoss Enterprise Application Platform 7; artemis-server as a component of Red Hat JBoss Enterprise Application Platform Expansion Pack · Fixed: eap8-activemq-artemis-0:2.40.0-8.redhat_00024.1.el10eap.noarch as a component of Red Hat JBoss EAP 8.1 for RHEL 10; eap8-activemq-artemis-0:2.40.0-8.redhat_00024.1.el10eap.src as a component of Red Hat JBoss EAP 8.1 for RHEL 10; eap8-activemq-artemis-cli-0:2.40.0-8.redhat_00024.1.el10eap.noarch as a component of Red Hat JBoss EAP 8.1 for RHEL 10; eap8-activemq-artemis-commons-0:2.40.0-8.redhat_00024.1.el10eap.noarch as a component of Red Hat JBoss EAP 8.1 for RHEL 10; eap8-activemq-artemis-core-client-0:2.40.0-8.redhat_00024.1.el10eap.noarch as a component of Red Hat JBoss EAP 8.1 for RHEL 10; eap8-activemq-artemis-dto-0:2.40.0-8.redhat_00024.1.el10eap.noarch as a component of Red Hat JBoss EAP 8.1 for RHEL 10; eap8-activemq-artemis-hornetq-protocol-0:2.40.0-8.redhat_00024.1.el10eap.noarch as a component of Red Hat JBoss EAP 8.1 for RHEL 10; eap8-activemq-artemis-hqclient-protocol-0:2.40.0-8.redhat_00024.1.el10eap.noarch as a component of Red Hat JBoss EAP 8.1 for RHEL 10; eap8-activemq-artemis-jakarta-client-0:2.40.0-8.redhat_00024.1.el10eap.noarch as a component of Red Hat JBoss EAP 8.1 for RHEL 10; eap8-activemq-artemis-jakarta-ra-0:2.40.0-8.redhat_00024.1.el10eap.noarch as a component of Red Hat JBoss EAP 8.1 for RHEL 10; eap8-activemq-artemis-jakarta-server-0:2.40.0-8.redhat_00024.1.el10eap.noarch as a component of Red Hat JBoss EAP 8.1 for RHEL 10; eap8-activemq-artemis-jakarta-service-extensions-0:2.40.0-8.redhat_00024.1.el10eap.noarch as a component of Red Hat JBoss EAP 8.1 for RHEL 10; eap8-activemq-artemis-jdbc-store-0:2.40.0-8.redhat_00024.1.el10eap.noarch as a component of Red Hat JBoss EAP 8.1 for RHEL 10; eap8-activemq-artemis-journal-0:2.40.0-8.redhat_00024.1.el10eap.noarch as a component of Red Hat JBoss EAP 8.1 for RHEL 10; eap8-activemq-artemis-selector-0:2.40.0-8.redhat_00024.1.el10eap.noarch as a component of Red Hat JBoss EAP 8.1 for RHEL 10; eap8-activemq-artemis-server-0:2.40.0-8.redhat_00024.1.el10eap.noarch as a component of Red Hat JBoss EAP 8.1 for RHEL 10; eap8-apache-cxf-0:4.1.7-1.SP1_redhat_00001.1.el10eap.noarch as a component of Red Hat JBoss EAP 8.1 for RHEL 10; eap8-apache-cxf-0:4.1.7-1.SP1_redhat_00001.1.el10eap.src as a component of Red Hat JBoss EAP 8.1 for RHEL 10; eap8-apache-cxf-rt-0:4.1.7-1.SP1_redhat_00001.1.el10eap.noarch as a component of Red Hat JBoss EAP 8.1 for RHEL 10; eap8-apache-cxf-services-0:4.1.7-1.SP1_redhat_00001.1.el10eap.noarch as a component of Red Hat JBoss EAP 8.1 for RHEL 10; eap8-apache-cxf-tools-0:4.1.7-1.SP1_redhat_00001.1.el10eap.noarch as a component of Red Hat JBoss EAP 8.1 for RHEL 10; eap8-artemis-wildfly-integration-0:2.0.5-1.Final_redhat_00001.1.el10eap.noarch as a component of Red Hat JBoss EAP 8.1 for RHEL 10; eap8-artemis-wildfly-integration-0:2.0.5-1.Final_redhat_00001.1.el10eap.src as a component of Red Hat JBoss EAP 8.1 for RHEL 10; eap8-bouncycastle-0:1.85.0-1.redhat_00001.1.el10eap.noarch as a component of Red Hat JBoss EAP 8.1 for RHEL 10; eap8-bouncycastle-0:1.85.0-1.redhat_00001.1.el10eap.src as a component of Red Hat JBoss EAP 8.1 for RHEL 10; eap8-bouncycastle-jmail-0:1.85.0-1.redhat_00001.1.el10eap.noarch as a component of Red Hat JBoss EAP 8.1 for RHEL 10; eap8-bouncycastle-pg-0:1.85.0-1.redhat_00001.1.el10eap.noarch as a component of Red Hat JBoss EAP 8.1 for RHEL 10; eap8-bouncycastle-pkix-0:1.85.0-1.redhat_00001.1.el10eap.noarch as a component of Red Hat JBoss EAP 8.1 for RHEL 10; eap8-bouncycastle-prov-0:1.85.0-1.redhat_00001.1.el10eap.noarch as a component of Red Hat JBoss EAP 8.1 for RHEL 10; eap8-bouncycastle-util-0:1.85.0-1.redhat_00001.1.el10eap.noarch as a component of Red Hat JBoss EAP 8.1 for RHEL 10; and 415 more
    Red Hat Product Security ↗
  4. Affected versionsThe structured affected or fixed version information changed.
    Before
    Apache Artemis: 2.50.0 ≤ 2.56.0; Apache ActiveMQ Artemis: 1.0.0 ≤ 2.44.0 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    Apache Artemis: 2.50.0 ≤ 2.56.0; Apache ActiveMQ Artemis: 1.0.0 ≤ 2.44.0 · Fixed: Before applying the update, back up your existing installation, including all applications, configuration files, databases and database settings. The References section of this erratum contains a download link (you must log in to download the update).
    Red Hat Product Security ↗
  5. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    Red Hat Product Security ↗
  6. Vendor guidanceAuthoritative vendor guidance changed: added vendor advisory: lists.apache.org/syjch88zw6pfdoso9vs46m23xkgxjbxo.
    Before
    no authoritative guidance recorded
    After
    vendor advisory: lists.apache.org/syjch88zw6pfdoso9vs46m23xkgxjbxo
    security@apache.org ↗
  7. Affected versionsThe structured affected or fixed version information changed.
    Before
    2.50.0 ≤ 2.56.0; 1.0.0 ≤ 2.44.0 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    Apache Artemis: 2.50.0 ≤ 2.56.0; Apache ActiveMQ Artemis: 1.0.0 ≤ 2.44.0 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    CNA ↗
  8. SeveritySeverity changed from Unknown to High.
    Before
    Unknown
    After
    High
    CISA ADP ↗
  9. CVSS scoreCVSS score changed from not recorded to 7.5 (CVSS 3.1 · CISA ADP · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N).
    Before
    not recorded
    After
    7.5 (CVSS 3.1 · CISA ADP · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N)
    CISA ADP ↗
  10. ENISA EUVD mappingEUVD-2026-75249 was added to the official ENISA EUVD mapping for this CVE.
    Before
    not recorded
    After
    {"euvdId":"EUVD-2026-75249"}
    ENISA EUVD ↗
  11. Catalogue recordCVE added to the BlackTree catalogue.
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release recorded from official guidance
Fixed release recorded from official guidance
ENISA EUVD · EUVD-2026-75249↗Red Hat Product Security security advisory↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-49363 · cve.blacktree.nl