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

Apache ActiveMQ Broker, Apache ActiveMQ, Apache ActiveMQ All: Durable Subscription Disclosure via Crafted BrokerInfo (OpenWire)

Apache Software Foundation · Apache ActiveMQ Broker

5.9MediumCVSS 3.1
Recommended action
Scheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Fix not verified
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Medium, 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.51% for the current model date.

Compensating controls

  • 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 ActiveMQ Broker and falls inside the recorded affected range.
  2. Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
  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: As exposure requiresRemediation target: Within 365 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.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

4 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourceactivemqAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourceactivemqAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourceactivemqAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archiveactivemqUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Open-source package ranges12 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
Mavenorg.apache.activemq:activemq-allECOSYSTEM: introduced 0; fixed 5.19.75.19.7OSV record ↗aggregator derived · 10 Sep 2026
Mavenorg.apache.activemq:activemq-allECOSYSTEM: introduced 6.0.0; fixed 6.2.66.2.6OSV record ↗aggregator derived · 10 Sep 2026
Mavenorg.apache.activemq:activemq-brokerECOSYSTEM: introduced 0; fixed 5.19.75.19.7OSV record ↗aggregator derived · 10 Sep 2026
Mavenorg.apache.activemq:activemq-brokerECOSYSTEM: introduced 6.0.0; fixed 6.2.66.2.6OSV record ↗aggregator derived · 10 Sep 2026
Mavenorg.apache.activemq:apache-activemqECOSYSTEM: introduced 0; fixed 5.19.75.19.7OSV record ↗aggregator derived · 10 Sep 2026
Mavenorg.apache.activemq:apache-activemqECOSYSTEM: introduced 6.0.0; fixed 6.2.66.2.6OSV record ↗aggregator derived · 10 Sep 2026
mavenorg.apache.activemq:activemq-all< 5.19.75.19.7GitHub advisory ↗github reviewed aggregator · 9 Jul 2026
mavenorg.apache.activemq:activemq-all>= 6.0.0, < 6.2.66.2.6GitHub advisory ↗github reviewed aggregator · 9 Jul 2026
mavenorg.apache.activemq:activemq-broker< 5.19.75.19.7GitHub advisory ↗github reviewed aggregator · 9 Jul 2026
mavenorg.apache.activemq:activemq-broker>= 6.0.0, < 6.2.66.2.6GitHub advisory ↗github reviewed aggregator · 9 Jul 2026
mavenorg.apache.activemq:apache-activemq< 5.19.75.19.7GitHub advisory ↗github reviewed aggregator · 9 Jul 2026
mavenorg.apache.activemq:apache-activemq>= 6.0.0, < 6.2.66.2.6GitHub advisory ↗github reviewed aggregator · 9 Jul 2026
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-33573

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

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
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Fix not verified
01

What, why and how

Exposure of Sensitive Information Through Metadata vulnerability in Apache ActiveMQ Broker, Apache ActiveMQ, Apache ActiveMQ All. Brokers that are configured with a network connector with syncDurableSubs set to true, are vulnerable to an unauthenticated attacker who can receive a list of all durable topic subscriptions in the broker, including client identifiers, subscription names, topic destinations, and JMS selector expressions, by sending a BrokerInfo command. The broker incorrectly responds without first ensuring the connection is authenticated. This issue affects Apache ActiveMQ Broker: before 5.19.7, from 6.0.0 before 6.2.6; Apache ActiveMQ: before 5.19.7, from 6.0.0 before 6.2.6; Apache ActiveMQ All: before 5.19.7, from 6.0.0 before 6.2.6. Users are recommended to upgrade to version 6.2.6 or 5.19.7, which fixes the issue.

What

Exposure of Sensitive Information Through Metadata vulnerability in Apache ActiveMQ Broker, Apache ActiveMQ, Apache ActiveMQ All. Brokers that are configured with a network connector with syncDurableSubs set to true, are vulnerable to an unauthenticated attacker who can receive a list of all durable topic subscriptions in the broker, including client identifiers, subscription names, topic destinations, and JMS selector expressions, by sending a BrokerInfo command. The broker incorrectly responds without first ensuring the connection is authenticated. This issue affects Apache ActiveMQ Broker: before 5.19.7, from 6.0.0 before 6.2.6; Apache ActiveMQ: before 5.19.7, from 6.0.0 before 6.2.6; Apache ActiveMQ All: before 5.19.7, from 6.0.0 before 6.2.6. Users are recommended to upgrade to version 6.2.6 or 5.19.7, which fixes the issue.

Why

The product prevents direct access to a resource containing sensitive information, but it does not sufficiently limit access to metadata that is derived from the original, sensitive information.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may obtain information outside the intended access boundary.

What

Exposure of Sensitive Information Through Metadata vulnerability in Apache ActiveMQ Broker, Apache ActiveMQ, Apache ActiveMQ All. Brokers that are configured with a network connector with syncDurableSubs set to true, are vulnerable to an unauthenticated attacker who can receive a list of all durable topic subscriptions in the broker, including client identifiers, subscription names, topic destinations, and JMS selector expressions, by sending a BrokerInfo command. The broker incorrectly responds without first ensuring the connection is authenticated. This issue affects Apache ActiveMQ Broker: before 5.19.7, from 6.0.0 before 6.2.6; Apache ActiveMQ: before 5.19.7, from 6.0.0 before 6.2.6; Apache ActiveMQ All: before 5.19.7, from 6.0.0 before 6.2.6. Users are recommended to upgrade to version 6.2.6 or 5.19.7, which fixes the issue.

Why

The product prevents direct access to a resource containing sensitive information, but it does not sufficiently limit access to metadata that is derived from the original, sensitive information.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may obtain information outside the intended access boundary.

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 → Exposure of Sensitive Information Through Metadata → obtain information outside the intended access boundary
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
High: exploitation depends on specific conditions
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-1230 ↗

CWE-1230: Exposure of Sensitive Information Through Metadata. The product prevents direct access to a resource containing sensitive information, but it does not sufficiently limit access to metadata that is derived from the original, sensitive information.

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:H/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.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.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-1230
A

Official authority intelligence

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

BSI · German · WID-SEC-2026-3043IBM QRadar SIEM: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM QRadar SIEM ausnutzen, um Sicherheitsvorkehrungen zu umgehen, um seine Privilegien zu erhöhen, um einen Denial of Service Angriff durchzuführen, um Informationen offenzulegen, um Dateien zu manipulieren, um einen Cross-Site Scripting Angriff durchzuführen und um beliebigen Programmcode auszuführen.

Official advisory ↗
BSI · German · WID-SEC-2026-1741Apache ActiveMQ: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Apache ActiveMQ ausnutzen, um einen Cross-Site Scripting Angriff durchzuführen, Informationen offenzulegen, seine Rechte zu erweitern, Daten zu manipulieren und Code auszuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260603Security Bulletin 3 Jun 2026

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

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1094Multiples vulnérabilités dans les produits IBM

ord?id=CVE-2026-48710 Référence CVE CVE-2026-48713 https://www.cve.org/CVERecord?id=CVE-2026-48713 Référence CVE CVE-2026-48775 https://www.cve.org/CVERecord?id=CVE-2026-48775 Référence CVE CVE-2026-48779 https://www.cve.org/CVERecord?id=CVE-2026-48779 Référence CVE CVE-2026-4878 https://www.cve.org/CVERecord?id=CVE-2026-4878 Référence CVE CVE-2026-48801 https://www.cve.org/CVERecord?id=CVE-2026-48801 Référence CVE CVE-2026-48864 https://www.cve.org/CVERecord?id=CVE-2026-48864 Référence CVE CVE-2026-48988 https://www.cve.org/CVERecord?id=CVE-2026-48988 Référence CVE CVE-2026-49157 https://www.cve.org/CVERecord?id=CVE-2026-49157 Référence CVE CVE-2026-49270 https://www.cve.org/CVERecord?id=CVE-2026-49270 Référence CVE CVE-2026-49432 https://www.cve.org/CVERecord?id=CVE-2026-49432 Référence CVE CVE-2026-49434 https://www.cve.org/CVERecord?id=CVE-2026-49434 Référence CVE CVE-2026-49458 https://www.cve.org/CVERecord?id=CVE-2026-49458 Référence CVE CVE-2026-49459 https://www.cve.org/CVERecord?id=CVE-2026-49459 Référence CVE CVE-2026-49476 https://www.cve.org/CVERecord?id=CVE-2026-49476 Référence CVE CVE-2026-49477 https://www.cve.org/CVERecord?id=CVE-2026-49477 Référence CVE CVE-2026-49844 https://www.cve.org/CVERecord?id=CVE-2026-49844 Référence CVE CVE-2026-49978 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0958Multiples vulnérabilités dans les produits IBM

ERecord?id=CVE-2026-45505 Référence CVE CVE-2026-46595 https://www.cve.org/CVERecord?id=CVE-2026-46595 Référence CVE CVE-2026-46597 https://www.cve.org/CVERecord?id=CVE-2026-46597 Référence CVE CVE-2026-46598 https://www.cve.org/CVERecord?id=CVE-2026-46598 Référence CVE CVE-2026-46605 https://www.cve.org/CVERecord?id=CVE-2026-46605 Référence CVE CVE-2026-4786 https://www.cve.org/CVERecord?id=CVE-2026-4786 Référence CVE CVE-2026-4800 https://www.cve.org/CVERecord?id=CVE-2026-4800 Référence CVE CVE-2026-4867 https://www.cve.org/CVERecord?id=CVE-2026-4867 Référence CVE CVE-2026-49157 https://www.cve.org/CVERecord?id=CVE-2026-49157 Référence CVE CVE-2026-49270 https://www.cve.org/CVERecord?id=CVE-2026-49270 Référence CVE CVE-2026-49844 https://www.cve.org/CVERecord?id=CVE-2026-49844 Référence CVE CVE-2026-5038 https://www.cve.org/CVERecord?id=CVE-2026-5038 Référence CVE CVE-2026-5079 https://www.cve.org/CVERecord?id=CVE-2026-5079 Référence CVE CVE-2026-53550 https://www.cve.org/CVERecord?id=CVE-2026-53550 Référence CVE CVE-2026-53655 https://www.cve.org/CVERecord?id=CVE-2026-53655 Référence CVE CVE-2026-54500 https://www.cve.org/CVERecord?id=CVE-2026-54500 Référence CVE CVE-2026-54502 https://www.cve.org/CVERecord?id=CVE-2026-54502 Référence CVE CVE-2026-54592 https://www.cve.org/CVERecord?id=CVE-

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-022351Apache Software FoundationのApache ActiveMQ等の複数製品におけるリソースの枯渇に関する脆弱性

Apache ActiveMQ Broker、Apache ActiveMQ、Apache ActiveMQ All における、メモリ不足（Out of Memory、OOM）を利用したサービス拒否（DoS）の脆弱性。CVE-2026-49270 の修正に伴い、未認証の攻撃者が ConnectionInfo を送信せずに BrokerInfo コマンドを繰り返し送信することで、ブローカーを OOM 状態に追い込み、最終的に OOM によりクラッシュさせることが可能になりました。この問題は次のバージョンに影響します。Apache ActiveMQ Broker: 5.19.7 から 5.19.8 未満、6.2.6 から 6.2.7 未満。Apache ActiveMQ: 5.19.7 から 5.19.8 未満、6.2.6 から 6.2.7 未満。Apache ActiveMQ All: 5.19.7 から 5.19.8 未満、6.2.6 から 6.2.7 未満。ユーザーは問題を修正したバージョン 6.2.7 へのアップグレードを推奨します。

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-017745Apache Software FoundationのApache ActiveMQ等の複数製品におけるメタデータのよる重要な情報の公開に関する脆弱性

Apache ActiveMQ Broker、Apache ActiveMQ、およびApache ActiveMQ Allにおけるメタデータを通じた機密情報漏洩の脆弱性があります。syncDurableSubsがtrueに設定されたネットワークコネクタを持つブローカーは、認証されていない攻撃者がBrokerInfoコマンドを送信することで、クライアント識別子、サブスクリプション名、トピック宛先、JMSセレクタ式を含む、ブローカー内のすべてのdurableトピックサブスクリプションの一覧を受信できます。この脆弱性は、ブローカーが接続の認証を確認せずに誤って応答することに起因します。この問題はApache ActiveMQ Brokerのバージョン5.19.7未満、6.0.0以降6.2.6未満、およびApache ActiveMQとApache ActiveMQ Allの同じバージョン範囲に影響します。ユーザーは問題を修正したバージョン6.2.6または5.19.7へのアップグレードを推奨します。

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.
Fix not verified
Affected
  • Apache ActiveMQ Broker: 5.14.0 < 5.19.7, 6.0.0 < 6.2.6
  • Apache ActiveMQ: 5.14.0 < 5.19.7, 6.0.0 < 6.2.6
  • Apache ActiveMQ All: 5.14.0 < 5.19.7, 6.0.0 < 6.2.6
Fixed
No fixed version is explicitly recorded in the structured CVE data.
Action
No verified patch reference is present in the current structured sources. Check the vendor advisory before making a change.
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 1 Jun 2026 · Last source change 1 Jun 2026, 13:11 UTC · CWE-1230 · Exposure of Sensitive Information Through Metadata

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-08-14
European sourceENISA EUVD · EUVD-2026-33573
Product sourceCNA
Remediation sourceCVE/CNA references
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 ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
ENISA EUVD · EUVD-2026-33573↗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-49270 · cve.blacktree.nl