CVE-2026-26448: Use After Free

Published Aug 26, 2026
·
Updated

Stomper 5e2741e is vulnerable to Use-After-Free. When a client sends multiple CONNECT frames on the same TCP connection, and subsequently another client (or a later connection) sends SEND frames to a destination previously subscribed on that connection, the broker may dereference a pointer to a StompStreamSocket object that has already been freed. This results in a heap use-after-free and process crash. Because the protocol does not authenticate or restrict such sequences by default.

Affected Software

1 affected component
Stomper=5e2741e

Event History

Aug 26, 2026
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
Description
Data Sourced
via NVD·08:17 PM
Description

Frequently Asked Questions

1

Who can trigger the crash?

Any client able to connect to the broker can trigger the vulnerable frame sequence, because the protocol does not authenticate or restrict these sequences by default.

2

What interaction is required to exploit the issue?

An attacker sends multiple CONNECT frames on one TCP connection. A subsequent SEND frame from another client or a later connection to a destination previously subscribed on that connection can cause the broker to dereference the freed object and crash.

3

What is the observable impact?

The reported impact is a heap use-after-free that crashes the broker process.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203