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

Apache ActiveMQ Client, Apache ActiveMQ, Apache ActiveMQ All: Pre-authentication OpenWire memory-allocation DoS during wire format negotiation

Apache Software Foundation · Apache ActiveMQ Client

7.5HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 3 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
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.74% 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 ActiveMQ Client 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.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 3 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

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
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 3 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

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
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-50734 · CSAF 2.0 · revision 3 · finalRed Hat Product SecurityApache ActiveMQ Client: Apache ActiveMQ: Apache ActiveMQ All: Apache ActiveMQ: Denial of Service via crafted WireFormatInfo frame
76 known affected

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

  • activemq-artemis-native as a component of Red Hat AMQ Broker 7
  • activemq-openwire-legacy as a component of Red Hat AMQ Broker 7
  • apache-artemis as a component of Red Hat AMQ Broker 7
  • artemis-amqp-protocol as a component of Red Hat AMQ Broker 7
  • artemis-boot as a component of Red Hat AMQ Broker 7
  • artemis-cli as a component of Red Hat AMQ Broker 7
  • artemis-commons as a component of Red Hat AMQ Broker 7
  • artemis-console as a component of Red Hat AMQ Broker 7
  • artemis-console-war as a component of Red Hat AMQ Broker 7
  • artemis-core-client as a component of Red Hat AMQ Broker 7
  • artemis-dto as a component of Red Hat AMQ Broker 7
  • artemis-hornetq-protocol as a component of Red Hat AMQ Broker 7
Summary
A flaw was found in Apache ActiveMQ. An unauthenticated network attacker can exploit this vulnerability by sending a specially crafted WireFormatInfo frame with an excessively large size value. This unvalidated value causes the broker to attempt an oversized memory allocation during pre-authentication negotiation. Consequently, this can lead to an Out Of Memory (OOM) error, resulting in a Denial of Service (DoS) and crashing the broker.
Remediation
Before applying this update, make sure all previously released errata relevant to your system have been applied. 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-40282

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 actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 3 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

Memory Allocation with Excessive Size Value vulnerability in Apache ActiveMQ Client, Apache ActiveMQ, Apache ActiveMQ All. An unauthenticated network attacker can cause a broker DoS by sending a crafted WireFormatInfo frame with a malicious large size value. The value is not validate and causes the broker to attempt allocation during pre-auth negotiation which can trigger OOM and crash the broker. This issue affects Apache ActiveMQ Client: before 5.19.8, from 6.0.0 before 6.2.7; Apache ActiveMQ: before 5.19.8, from 6.0.0 before 6.2.7; Apache ActiveMQ All: before 5.19.8, from 6.0.0 before 6.2.7. Users are recommended to upgrade to version 6.2.7 or 5.19.8, which fixes the issue.

What

Memory Allocation with Excessive Size Value vulnerability in Apache ActiveMQ Client, Apache ActiveMQ, Apache ActiveMQ All. An unauthenticated network attacker can cause a broker DoS by sending a crafted WireFormatInfo frame with a malicious large size value. The value is not validate and causes the broker to attempt allocation during pre-auth negotiation which can trigger OOM and crash the broker. This issue affects Apache ActiveMQ Client: before 5.19.8, from 6.0.0 before 6.2.7; Apache ActiveMQ: before 5.19.8, from 6.0.0 before 6.2.7; Apache ActiveMQ All: before 5.19.8, from 6.0.0 before 6.2.7. Users are recommended to upgrade to version 6.2.7 or 5.19.8, which fixes the issue.

Why

The product allocates memory based on an untrusted, large size value, but it does not ensure that the size is within expected limits, allowing arbitrary amounts of memory to be allocated.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.

What

Memory Allocation with Excessive Size Value vulnerability in Apache ActiveMQ Client, Apache ActiveMQ, Apache ActiveMQ All. An unauthenticated network attacker can cause a broker DoS by sending a crafted WireFormatInfo frame with a malicious large size value. The value is not validate and causes the broker to attempt allocation during pre-auth negotiation which can trigger OOM and crash the broker. This issue affects Apache ActiveMQ Client: before 5.19.8, from 6.0.0 before 6.2.7; Apache ActiveMQ: before 5.19.8, from 6.0.0 before 6.2.7; Apache ActiveMQ All: before 5.19.8, from 6.0.0 before 6.2.7. Users are recommended to upgrade to version 6.2.7 or 5.19.8, which fixes the issue.

Why

The product allocates memory based on an untrusted, large size value, but it does not ensure that the size is within expected limits, allowing arbitrary amounts of memory to be allocated.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.

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 → Memory Allocation with Excessive Size Value → disrupt the affected service
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-789 ↗

CWE-789: Memory Allocation with Excessive Size Value. The product allocates memory based on an untrusted, large size value, but it does not ensure that the size is within expected limits, allowing arbitrary amounts of memory to be allocated.

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:N/I:N/A:H

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.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
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.
NetworkUnauthenticatedDenial of serviceCWE-789
A

Official authority intelligence

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

BSI · German · WID-SEC-2026-3403Oracle Communications: Mehrere Schwachstellen

Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in Oracle Communications ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

Official advisory ↗
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-2124Apache ActiveMQ: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Apache ActiveMQ ausnutzen, um Sicherheitsmaßnahmen zu umgehen, Cross-Site-Scripting-Angriffe durchzuführen oder einen Denial-of-Service-Zustand zu verursachen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260701Security Bulletin 1 July 2026

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

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

d?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-49851 https://www.cve.org/CVERecord?id=CVE-2026-49851 Référence CVE CVE-2026-50010 https://www.cve.org/CVERecord?id=CVE-2026-50010 Référence CVE CVE-2026-50011 https://www.cve.org/CVERecord?id=CVE-2026-50011 Référence CVE CVE-2026-50020 https://www.cve.org/CVERecord?id=CVE-2026-50020 Référence CVE CVE-2026-50560 https://www.cve.org/CVERecord?id=CVE-2026-50560 Référence CVE CVE-2026-50645 https://www.cve.org/CVERecord?id=CVE-2026-50645 Référence CVE CVE-2026-50734 https://www.cve.org/CVERecord?id=CVE-2026-50734 Référence CVE CVE-2026-53537 https://www.cve.org/CVERecord?id=CVE-2026-53537 Référence CVE CVE-2026-53538 https://www.cve.org/CVERecord?id=CVE-2026-53538 Référence CVE CVE-2026-53539 https://www.cve.org/CVERecord?id=CVE-2026-53539 Référence CVE CVE-2026-53540 https://www.cve.org/CVERecord?id=CVE-2026-53540 Référence CVE CVE-2026-53917 https://www.cve.org/CVERecord?id=CVE-2026-53917 Référence CVE CVE-2026-54225 https://www.cve.org/CVERecord?id=CVE-2026-54225 Référence CVE CVE-2026-54282 https://www.cve.org/CVERecord?id=CVE-2026-54282 Référence CVE CVE-2026-54283 https://www.cve.org/CVERecord?id=

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

ord?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=CVE-2026-49978 Référence CVE CVE-2026-5038 https://www.cve.org/CVERecord?id=CVE-2026-5038 Référence CVE CVE-2026-50645 https://www.cve.org/CVERecord?id=CVE-2026-50645 Référence CVE CVE-2026-50721 https://www.cve.org/CVERecord?id=CVE-2026-50721 Référence CVE CVE-2026-50722 https://www.cve.org/CVERecord?id=CVE-2026-50722 Référence CVE CVE-2026-50734 https://www.cve.org/CVERecord?id=CVE-2026-50734 Référence CVE CVE-2026-5078 https://www.cve.org/CVERecord?id=CVE-2026-5078 Référence CVE CVE-2026-5079 https://www.cve.org/CVERecord?id=CVE-2026-5079 Référence CVE CVE-2026-5260 https://www.cve.org/CVERecord?id=CVE-2026-5260 Référence CVE CVE-2026-52923 https://www.cve.org/CVERecord?id=CVE-2026-52923 Référence CVE CVE-2026-52993 https://www.cve.org/CVERecord?id=CVE-2026-52993 Référence CVE CVE-2026-53006 https://www.cve.org/CVERecord?id=CVE-2026-53006 Référence CVE CVE-2026-53059 https://www.cve.org/CVERecord?id=CVE-2026-53059 Référence CVE CVE-2026-53071 https://www.cve.org/CVERecord?id=CVE-20

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

d?id=CVE-2026-48962 Référence CVE CVE-2026-48978 https://www.cve.org/CVERecord?id=CVE-2026-48978 Référence CVE CVE-2026-49268 https://www.cve.org/CVERecord?id=CVE-2026-49268 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-50151 https://www.cve.org/CVERecord?id=CVE-2026-50151 Référence CVE CVE-2026-50162 https://www.cve.org/CVERecord?id=CVE-2026-50162 Référence CVE CVE-2026-50163 https://www.cve.org/CVERecord?id=CVE-2026-50163 Référence CVE CVE-2026-50645 https://www.cve.org/CVERecord?id=CVE-2026-50645 Référence CVE CVE-2026-50734 https://www.cve.org/CVERecord?id=CVE-2026-50734 Référence CVE CVE-2026-53916 https://www.cve.org/CVERecord?id=CVE-2026-53916 Référence CVE CVE-2026-53917 https://www.cve.org/CVERecord?id=CVE-2026-53917 Référence CVE CVE-2026-54399 https://www.cve.org/CVERecord?id=CVE-2026-54399 Référence CVE CVE-2026-54428 https://www.cve.org/CVERecord?id=CVE-2026-54428 Référence CVE CVE-2026-54475 https://www.cve.org/CVERecord?id=CVE-2026-54475 Référence CVE CVE-2026-54512 https://www.cve.org/CVERecord?id=CVE-2026-54512 Référence CVE CVE-2026-54513 https://www.cve.org/CVERecord?id=CVE-2026-54513 Référence CVE CVE-2026-54514 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-022352Apache Software FoundationのApache ActiveMQにおける過剰なサイズ値のメモリ割り当てに関する脆弱性

Apache ActiveMQ Client、Apache ActiveMQ、Apache ActiveMQ Allにおいて、過剰なサイズ値を指定したメモリ割り当ての脆弱性があります。認証されていないネットワーク攻撃者が、悪意のある大きなサイズ値を含む細工されたWireFormatInfoフレームを送信することで、ブローカーのDoSを引き起こす可能性があります。このサイズ値は検証されず、認証前のネゴシエーション中にブローカーが割り当てを試みるため、OOM（メモリ不足）を引き起こし、結果としてブローカーがクラッシュすることがあります。本脆弱性は、Apache ActiveMQ Clientの5.19.8より前のバージョン、および6.0.0から6.2.7より前のバージョン、Apache ActiveMQの5.19.8より前のバージョン、および6.0.0から6.2.7より前のバージョン、さらにApache ActiveMQ Allの5.19.8より前のバージョン、および6.0.0から6.2.7より前のバージョンに影響を与えます。利用者は、本問題に対処したバージョン6.2.7または5.19.8にアップグレードすることを推奨します。

Official advisory ↗
NCSC-NL · Dutch · NCSC-2026-0375Kwetsbaarheden verholpen in Oracle Communications

An unauthenticated network attacker can exploit a vulnerability in Apache ActiveMQ's WireFormatInfo frame handling to cause out-of-memory errors and Denial of Service (DoS), affecting multiple versions including Oracle Communications Unified Assurance and Red Hat AMQ Broker.

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 availability varies by product
Affected
Fixed
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
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 30 Jun 2026 · Last source change 30 Jun 2026, 12:32 UTC · CWE-789 · Memory Allocation with Excessive Size Value

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-40282
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
    < 5.19.8; 6.0.0 < 6.2.7 · 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
    < 5.19.8; 6.0.0 < 6.2.7 · Fixed: Before applying this update, make sure all previously released errata relevant to your system have been applied. 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-50734 to remediation: access.redhat.com/CVE-2026-50734.
    Before
    remediation: access.redhat.com/CVE-2026-50734
    After
    remediation: access.redhat.com/CVE-2026-50734
    Red Hat Product Security ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    activemq-artemis-native as a component of Red Hat AMQ Broker 7; activemq-openwire-legacy as a component of Red Hat AMQ Broker 7; apache-artemis as a component of Red Hat AMQ Broker 7; artemis-amqp-protocol as a component of Red Hat AMQ Broker 7; artemis-boot as a component of Red Hat AMQ Broker 7; artemis-cli as a component of Red Hat AMQ Broker 7; artemis-commons as a component of Red Hat AMQ Broker 7; artemis-console as a component of Red Hat AMQ Broker 7; artemis-console-war as a component of Red Hat AMQ Broker 7; artemis-core-client as a component of Red Hat AMQ Broker 7; artemis-dto as a component of Red Hat AMQ Broker 7; artemis-hornetq-protocol as a component of Red Hat AMQ Broker 7; artemis-hqclient-protocol as a component of Red Hat AMQ Broker 7; artemis-jdbc-store as a component of Red Hat AMQ Broker 7; artemis-jms-client as a component of Red Hat AMQ Broker 7; artemis-jms-server as a component of Red Hat AMQ Broker 7; artemis-journal as a component of Red Hat AMQ Broker 7; artemis-lockmanager-api as a component of Red Hat AMQ Broker 7; artemis-lockmanager-ri as a component of Red Hat AMQ Broker 7; artemis-mqtt-protocol as a component of Red Hat AMQ Broker 7; artemis-openwire-protocol as a component of Red Hat AMQ Broker 7; artemis-ra as a component of Red Hat AMQ Broker 7; artemis-selector as a component of Red Hat AMQ Broker 7; artemis-server as a component of Red Hat AMQ Broker 7; artemis-service-extensions as a component of Red Hat AMQ Broker 7; artemis-stomp-protocol as a component of Red Hat AMQ Broker 7; artemis-web as a component of Red Hat AMQ Broker 7; libartemis-native-linux-aarch64 as a component of Red Hat AMQ Broker 7; libartemis-native-linux-i686 as a component of Red Hat AMQ Broker 7; libartemis-native-linux-ppc64le as a component of Red Hat AMQ Broker 7; and 47 more · Fixed: Red Hat AMQ Broker 7.13.6; Red Hat AMQ Broker 7.14.1
    After
    activemq-artemis-native as a component of Red Hat AMQ Broker 7; activemq-openwire-legacy as a component of Red Hat AMQ Broker 7; apache-artemis as a component of Red Hat AMQ Broker 7; artemis-amqp-protocol as a component of Red Hat AMQ Broker 7; artemis-boot as a component of Red Hat AMQ Broker 7; artemis-cli as a component of Red Hat AMQ Broker 7; artemis-commons as a component of Red Hat AMQ Broker 7; artemis-console as a component of Red Hat AMQ Broker 7; artemis-console-war as a component of Red Hat AMQ Broker 7; artemis-core-client as a component of Red Hat AMQ Broker 7; artemis-dto as a component of Red Hat AMQ Broker 7; artemis-hornetq-protocol as a component of Red Hat AMQ Broker 7; artemis-hqclient-protocol as a component of Red Hat AMQ Broker 7; artemis-jdbc-store as a component of Red Hat AMQ Broker 7; artemis-jms-client as a component of Red Hat AMQ Broker 7; artemis-jms-server as a component of Red Hat AMQ Broker 7; artemis-journal as a component of Red Hat AMQ Broker 7; artemis-lockmanager-api as a component of Red Hat AMQ Broker 7; artemis-lockmanager-ri as a component of Red Hat AMQ Broker 7; artemis-mqtt-protocol as a component of Red Hat AMQ Broker 7; artemis-openwire-protocol as a component of Red Hat AMQ Broker 7; artemis-ra as a component of Red Hat AMQ Broker 7; artemis-selector as a component of Red Hat AMQ Broker 7; artemis-server as a component of Red Hat AMQ Broker 7; artemis-service-extensions as a component of Red Hat AMQ Broker 7; artemis-stomp-protocol as a component of Red Hat AMQ Broker 7; artemis-web as a component of Red Hat AMQ Broker 7; libartemis-native-linux-aarch64 as a component of Red Hat AMQ Broker 7; libartemis-native-linux-i686 as a component of Red Hat AMQ Broker 7; libartemis-native-linux-ppc64le as a component of Red Hat AMQ Broker 7; and 46 more · Fixed: AMQ Clients 2026.Q3; Red Hat AMQ Broker 7.13.6; Red Hat AMQ Broker 7.14.1
    Red Hat Product Security ↗
  4. Affected versionsThe structured affected or fixed version information changed.
    Before
    < 5.19.8; 6.0.0 < 6.2.7 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    < 5.19.8; 6.0.0 < 6.2.7 · 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 ↗
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-40282↗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-50734 · cve.blacktree.nl