Skip to content
VulniPulse
Advisory severityHigh7.5Red Hat Linux

High [CVE-2026-49432] Denial of Service via improper input validation in STOMP connector

This high-severity Red Hat Linux advisory covers CVE-2026-49432 affecting Red Hat AMQ Broker 7.13.6, Red Hat AMQ Broker 7.14.1, Red Hat AMQ Clients.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-49432 Source published Source updated

VulniPulse record published Record updated

Affected products & platforms
Red Hat LinuxUnclassified
Open source advisory

Android app · Google Play

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

Improper Input Validation vulnerability in Apache ActiveMQ, Apache ActiveMQ All, Apache ActiveMQ Stomp. A remote unauthenticated peer that can reach an exposed STOMP connector can trigger denial-of-service behavior by sending a negative content-length.

For the NIO STOMP transport, an attacker can keep streaming body bytes and grow the per-connection command buffer beyond configured limits to cause OOM. For the blocking STOMP protocol, an error will instead force abnormal transport exception handling for the affected connection and closure.

Users are recommended to upgrade to version 6.2.7 or 5.19.8, which fixes the issue. This can lead to a denial of service (DoS) condition, either by consuming excessive memory and causing an Out-Of-Memory (OOM) error or by forcing the abnormal closure of affected connections.

Red Hat products ship Apache ActiveMQ Classic components as transitive dependencies. The vulnerability is in the Classic ActiveMQ STOMP connector's content-length validation, allowing an unauthenticated attacker to cause OOM via a negative content-length value.

Apache ActiveMQ Artemis, which powers Red Hat AMQ Broker, has its own STOMP protocol implementation (artemis-stomp-protocol) that does not share this code path. The Classic STOMP connector is not exposed in Red Hat product deployments.

Affected versions
  • < 5.19.8
  • < 6.0.0
  • < 6.2.7

Official advisory · high-confidence parse· fetched 21 days ago·verify at source

Fixed versions
  • 6.2.7
  • 5.19.8
  • artemis-stomp-protocol
  • RHSA-2026:66545
  • RHSA-2026:66488

Official advisory · high-confidence parse· fetched 21 days ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • 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.

Official advisory · high-confidence parse· fetched 21 days ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.