CVE-2026-26448

stomper: Stomper: Denial of Service via Use-After-Free

Published Aug 26, 2026 CVSS 3.1 · 9.8 Critical EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

Stomper version 5e2741e contains a use‑after‑free flaw that allows a client to crash the broker. When a user sends multiple CONNECT frames over the same TCP socket and later another client sends SEND frames to a previously subscribed destination, the broker may dereference a pointer to a StompStreamSocket object that has already been freed. This results in a heap use‑after‑free and a process crash. Because the STOMP protocol lacks default authentication or restriction for such sequences, an unauthenticated attacker can trigger the crash, leading to denial of service.

Affected Systems

The affected product is the Stomper messaging broker, specifically the 5e2741e revision. No vendor name is publicly listed; the application is deployed in environments that use the STOMP protocol for messaging.

Risk and Exploitability

The vulnerability, rated with a CVSS score of 9.8, is not listed in the CISA KEV catalog, and its EPSS score is below 1%, indicating a very low but nonzero probability of exploitation. Nevertheless, an unauthenticated remote client can induce a crash with a single TCP connection, making the risk high for availability. While the description does not report arbitrary code execution, a heap corruption could be leveraged by a sophisticated attacker if additional conditions are met. Brokers running Stomper should consider the risk as moderate to high, particularly in production environments where uninterrupted messaging is critical.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to the latest Stomper release that resolves the use‑after‑free bug.
  • Configure the broker to allow only a single CONNECT frame per TCP connection or enable authentication so that unauthorized clients cannot trigger the flaw.
  • Enforce network‑level filtering or segmentation to limit connections from untrusted hosts and monitor for repeated CONNECT/SEND sequences that may indicate an attempt to exploit the broker.

Generated by OpenCVE AI on September 1, 2026 at 14:23 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Title stomper: Stomper: Denial of Service via Use-After-Free
Weaknesses CWE-825
References
Metrics threat_severity

None

threat_severity

Important

Type Values Removed Values Added
Title Stomper Use-After-Free Leading to Broker Crash
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 9.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}

ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Title Stomper Use-After-Free Leading to Broker Crash
Weaknesses CWE-416
Type Values Removed Values Added
Description 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.
References

Subscriptions

No data.

Weaknesses

Sources

Status
PUBLISHED
Assigner
mitre
Published
Updated
Aug 27, 2026, 6:28 PM
Reserved
Feb 16, 2026, 12:00 AM
Status
Deferred
Published
Aug 26, 2026, 8:17 PM
Modified
Aug 28, 2026, 9:20 PM
Severity
Important
Public date
Aug 26, 2026, 12:00 AM