HighCVE-2026-50750

    Apache ActiveMQ Broker: Denial of Service (CVE-2026-50750)

    Published Last modified Sources: BSI, OSV, CVE.org

    What is affected, what to do

    Denial of Service via Out of Memory vulnerability in Apache ActiveMQ Broker, Apache ActiveMQ, Apache ActiveMQ All. Following the fix for CVE-2026-49270 an unauthenticated attacker can now cause broker OOM by sending an repeated BrokerInfo commands without sending a ConnectionInfo, until the broker will crash with OOM.

    Update Apache ActiveMQ Broker to version 5.19.8, Apache ActiveMQ Broker to version 6.2.7, Apache ActiveMQ to version 5.19.8.

    Affected
    • Apache ActiveMQ Broker lt 5.19.7..5.19.8
    • Apache ActiveMQ Broker lt 6.2.6..6.2.7
    • Apache ActiveMQ lt 5.19.7..5.19.8
    • Apache ActiveMQ lt 6.2.6..6.2.7
    • Apache ActiveMQ All lt 5.19.7..5.19.8
    • Apache ActiveMQ All lt 6.2.6..6.2.7
    Fixed in
    • Apache ActiveMQ Broker 5.19.8
    • Apache ActiveMQ Broker 6.2.7
    • Apache ActiveMQ 5.19.8
    • Apache ActiveMQ 6.2.7
    • Apache ActiveMQ All 5.19.8
    • Apache ActiveMQ All 6.2.7

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    7.5

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: NVD, CVSS v3

    7.5

    CVSS v3

    Severity High on the scale from 0 to 10.

    Source: BSI, OSV, CVE.org

    0.7 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 52.5

    Show all metrics
    Severity
    High
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    79.38 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    no public PoC known
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    7.5 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    7.5
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    0.7 %
    Low — model estimates < 1% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    52.5
    High — this CVE ranks above the median of all CVEs scored today (rank ≥ 36%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    —
    Published

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    Denial of Service via Out of Memory vulnerability in Apache ActiveMQ Broker, Apache ActiveMQ, Apache ActiveMQ All. Following the fix for CVE-2026-49270 an unauthenticated attacker can now cause broker OOM by sending an repeated BrokerInfo commands without sending a ConnectionInfo, until the broker will crash with OOM. This issue affects Apache ActiveMQ Broker: from 5.19.7 before 5.19.8, from 6.2.6 before 6.2.7; Apache ActiveMQ: from 5.19.7 before 5.19.8, from 6.2.6 before 6.2.7; Apache ActiveMQ All: from 5.19.7 before 5.19.8, from 6.2.6 before 6.2.7. Users are recommended to upgrade to version 6.2.7, which fixes the issue.

    Source: BSI WID Portal, BSI CSAF, OSV (Open Source Vulnerabilities), NVD (NIST), cvelistv5, CVE.org (MITRE)

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    Apache Software FoundationApache ActiveMQ
    • 5.19.7 – < 5.19.8
    • 6.2.6 – < 6.2.7
    • 5.19.8
    • 6.2.7
    Apache Software FoundationApache ActiveMQ All
    • 6.2.6 – < 6.2.7
    • 5.19.7 – < 5.19.8
    • 6.2.7
    • 5.19.8
    Apache Software FoundationApache ActiveMQ Broker
    • 6.2.6 – < 6.2.7
    • 5.19.7 – < 5.19.8
    • 6.2.7
    • 5.19.8
    apacheactivemq
    • 6.2.6
    • 5.19.7
    • —
    • —
    apacheactivemq_broker
    • 6.2.6
    • 5.19.7
    • —
    • —
    ApacheActiveMQ
    • < 6.2.7
    • < 5.19.8
    • 6.2.7
    • 5.19.8
    Distribution and container packages (2)

    Downstream packages (e.g. Bitnami, Debian, Ubuntu, Red Hat). Versions refer to the distribution, not the vendor.

    Distribution and container packages
    Affected versionsFixed in
    bitnamiactivemq
    • 5.19.7
    • 6.2.6
    • —
    • —

    Vendors and products

    References & sources

    Changes to this CVE

    Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

    1. Initial analysis by NVDNVD

      Newly listed as affected:
      Show 2 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Product configurationadded
      —
      OR *cpe:2.3:a:apache:activemq:5.19.7:*:*:*:*:*:*:* *cpe:2.3:a:apache:activemq:6.2.6:*:*:*:*:*:*:* *cpe:2.3:a:apache:activemq_broker:5.19.7:*:*:*:*:*:*:* *cpe:2.3:a:apache:activemq_broker:6.2.6:*:*:*:*:*:*:*
      Reference typeadded
      —
      Apache Software Foundation: https://lists.apache.org/thread/nhkmbdym61yp6wwy0dny8w1p46sm87kr Types: Mailing List, Vendor Advisory

      Source identifier: nvd@nist.gov

    2. ReceivedApache

      Description added or changed

      Show 3 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Affected versions (publisher)added
      —
      Apache ActiveMQ Broker, Apache ActiveMQ, Apache ActiveMQ All
      Descriptionadded
      —
      Denial of Service via Out of Memory vulnerability in Apache ActiveMQ Broker, Apache ActiveMQ, Apache ActiveMQ All. Following the fix for CVE-2026-49270 an unauthenticated attacker can now cause broker OOM by sending an repeated BrokerInfo commands without sending a ConnectionInfo, until the broker will crash with OOM. This issue affects Apache ActiveMQ Broker: from 5.19.7 before 5.19.8, from 6.2.6 before 6.2.7; Apache ActiveMQ: from 5.19.7 before 5.19.8, from 6.2.6 before 6.2.7; Apache ActiveMQ All: from 5.19.7 before 5.19.8, from 6.2.6 before 6.2.7. Users are recommended to upgrade to version 6.2.7, which fixes the issue.
      Referenceadded
      —
      https://lists.apache.org/thread/nhkmbdym61yp6wwy0dny8w1p46sm87kr

      Source identifier: security@apache.org

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2026-50750
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-50750"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-50750.svg?lang=en" alt="CVE-2026-50750 – NEOSEC Intel" height="20"></a>