How severe is CVE-2026-49270?

CVE-2026-49270 has a CVSS score of 5.9/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2026-49270?

CVE-2026-49270 affects the following packages: org.apache.activemq:apache-activemq (Maven), org.apache.activemq:apache-activemq (Maven), org.apache.activemq:activemq-broker (Maven), org.apache.activemq:activemq-broker (Maven), org.apache.activemq:activemq-all (Maven), org.apache.activemq:activemq-all (Maven). Ecosystems affected: Maven.

How do I fix CVE-2026-49270?

Update org.apache.activemq:apache-activemq to 5.19.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-49270 is resolved across your whole dependency graph.

How do I detect CVE-2026-49270 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.activemq:apache-activemq, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-49270 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2026-49270 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-49270 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-49270?

CVE-2026-49270 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 42th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-49270?

CVE-2026-49270 is classified as CWE-1230 (CWE-1230). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-49270 published, and has it been updated?

CVE-2026-49270 was published on June 1, 2026 and was last updated on October 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

MEDIUM severity

CVE-2026-49270 — apache-activemq

MEDIUM

CVE-2026-49270 is a medium-severity (CVSS 5.9) CWE-1230 vulnerability in org.apache.activemq:apache-activemq. A fix is available for org.apache.activemq:apache-activemq — see the affected versions and patch details below.

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

Also known asBIT-activemq-2026-49270GHSA-hf52-78x8-6w3w

Published

Jun 1, 2026

Updated

Oct 8, 2026

Affected

6 pkgs

Patched

6 / 6

Exploits

None indexed

Exploitation data as of Oct 14, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-49270.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs42th percentile — riskier than 42% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2026-49270 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 388,997 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

6 pkgs affected

☕org.apache.activemq:apache-activemq☕org.apache.activemq:apache-activemq☕org.apache.activemq:activemq-broker☕org.apache.activemq:activemq-broker☕org.apache.activemq:activemq-all☕org.apache.activemq:activemq-all

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

6 total 6 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.activemq:apache-activemq`	all versions	5.19.7`org.apache.activemq:apache-activemq:5.19.7`
☕Maven	`org.apache.activemq:apache-activemq`	≥ 6.0.0&&< 6.2.6	6.2.6`org.apache.activemq:apache-activemq:6.2.6`
☕Maven	`org.apache.activemq:activemq-broker`	all versions	5.19.7`org.apache.activemq:activemq-broker:5.19.7`
☕Maven	`org.apache.activemq:activemq-broker`	≥ 6.0.0&&< 6.2.6	6.2.6`org.apache.activemq:activemq-broker:6.2.6`
☕Maven	`org.apache.activemq:activemq-all`	all versions	5.19.7`org.apache.activemq:activemq-all:5.19.7`
☕Maven	`org.apache.activemq:activemq-all`	≥ 6.0.0&&< 6.2.6	6.2.6`org.apache.activemq:activemq-all:6.2.6`

Affected Products

2 products · 4 configurations

Application

activemqapache

≥ 6.0.0 && < 6.2.6

range

Application

activemq brokerapache

≥ 6.0.0 && < 6.2.6

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.activemq:apache-activemq, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.activemq:apache-activemq to 5.19.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-49270 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

Red Hat products ship Apache ActiveMQ Classic components as transitive dependencies. The vulnerability allows unauthenticated information disclosure via BrokerInfo commands when the broker has a network connector with syncDurableSubs=true configured. This is a non-default configuration specific to Classic ActiveMQ…

Workaround published by Red Hat

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Source: Red Hat security advisory for CVE-2026-49270 (CC BY 4.0)

Frequently Asked Questions

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:

O3 Security · Impact-Aware SCA

Is CVE-2026-49270 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

5.9/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

High

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

CWE Classification

CWE-1230CWE-1230

Weaponization

No known public exploit tooling found.

OpenSSF Scorecard

Package health score

activemq

7.0/10

Maintained10/10

Code-Review10/10

Branch-ProtectionN/A

Assessed Oct 12, 2026

Timeline

Disclosed

Jun 1, 2026

Last updated

Oct 8, 2026

Identifiers

CVE-2026-49270

GHSA-hf52-78x8-6w3w

BIT-activemq-2026-49270

References

Advisorygithub.com Advisorylists.apache.org Advisorynvd.nist.gov Webopenwall.com Webrepo.maven.apache.org Packagegithub.com

Related vulnerabilities

This CVE is medium severity; 8 of 8 other CVEs affecting apache-activemq are rated as high or higher (top: high).

CVE-2026-42253CVE-2026-49157CVE-2026-46605CVE-2026-42588CVE-2026-45505CVE-2026-41043CVE-2026-41044CVE-2026-40466

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 8, 2026

CVE-2026-49270 — apache-activemq

Exploitation Status

No confirmed exploitation observed yet

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2026-49270 in your dependencies?