Bug 2494846 (CVE-2026-53916) - CVE-2026-53916 activemq-stomp: Apache ActiveMQ, Apache ActiveMQ All, Apache ActiveMQ Stomp: Unbounded header buffer in STOMP NIO codec
Summary: CVE-2026-53916 activemq-stomp: Apache ActiveMQ, Apache ActiveMQ All, Apache A...
Keywords:
Status: NEW
Alias: CVE-2026-53916
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2495086 2495087
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-06-30 11:02 UTC by OSIDB Bzimport
Modified: 2026-09-10 23:25 UTC (History)
58 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2026:66488 0 None None None 2026-09-10 16:37:09 UTC
Red Hat Product Errata RHSA-2026:66545 0 None None None 2026-09-10 23:25:11 UTC

Description OSIDB Bzimport 2026-06-30 11:02:35 UTC 
Memory Allocation with Excessive Size Value vulnerability in Apache ActiveMQ, Apache ActiveMQ All, Apache ActiveMQ Stomp.


An unauthenticated client that opens a STOMP NIO connection can send header bytes that never terminate which makes the broker buffer them without limit, exhausting the JVM heap. 
This issue affects 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; Apache ActiveMQ Stomp: 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.
Comment 5 errata-xmlrpc 2026-09-10 16:37:05 UTC 
This issue has been addressed in the following products:

  Red Hat AMQ Broker 7.14.1

Via RHSA-2026:66488 https://access.redhat.com/errata/RHSA-2026:66488
Comment 6 errata-xmlrpc 2026-09-10 23:25:08 UTC 
This issue has been addressed in the following products:

  Red Hat AMQ Broker 7.13.6

Via RHSA-2026:66545 https://access.redhat.com/errata/RHSA-2026:66545
Note You need to log in before you can comment on or make changes to this bug.